I would like to see templates of sort, perhaps a visual editor. 

Take DashCode for example.

 

 

Scripting

• Command line support to build gadgets/widgets from a dxpack and a config file [1]
• Integrated support for script components (with event handling), so we can receive script events from a DestopX script [2]
• Better ActiveX controls
  • Password mode for the edit box without having to use a custom font
  • Expose and document more properties (some useful ones are already available but not documented like OnKeyDown events for listboxes)
• Expose animation properties to script (total number of frames, interval, flags)
• Proper debugger support for DesktopX scripts (so we can debug scripts in VS or Script Debugger with call stack/variable windows and breakpoints)
• Zip/Unzip functions available from script [3]
• Better cloning support (clone groups/use template/etc.)
• Fix the bug that prevents using more than 2 plugins in a gadget/widget.
• There is a lot of things to steal take inspiration from in Yahoo Widgets in terms of proper integration (using external ActiveX objects is nice, but each one has a different API, making using a lot of them a mess. And you can't connect to events easily, see [2])

[1] I'm post-processing dxpacks from outside DX to merge external scripts, modify scripts with #define/#ifdef/#ifndef, switch script components to release mode, etc. I'm using another instance of DX in a VM to export so I don't have to remove the dev version, load the final dxpack, export and then go back to the dev version. Being able to export the resulting dxpack directly from my build script will save me a lot of time!

[2] You can create a "controller" component that do all the work and receive other component events from there, but it would be cleaner to have that in the main script. It will save all the 1-line functions to forward DX events to the controller.

[3] Last time I checked the only Zip component universally available was the zip folder support in Windows, but the license doesn't allow third party use and it showed a progress dialog when unzipping. Exposing zip/unzip functions like in Yahoo widgets would be nice.

Yep , some kind of WYSIWYG would be great for complete nOoBz like me...

 

perhaps a nice free cash dispenser ?

  I shall have to ponder on this and come back with a wishlist.

Big wishes:

#1 TEMPLATES

Fully functional templates: Like the ones ID posted, where all the basic work is done and you just need to modify the look, or if you know how, modify the code and add more functions. The code for these templates should not be neglected either; they should be fully commented, streamlined, and easy to understand if you have basic knowledge of vbscript.

Component templates: Much like the ones we have in the DesktopX tutorial folder; rotating object, growing object, glowing object. Stuff that can be imported and used as part of a larger theme or widget. You could use the component as is or just take the script and use that.

#2 Pre-Configured Objects

This is pretty much to reduce the amount of time a user spends making choices, configurations, combinations of choices and configurations, and choices between combinations of choices and configurations.

The basic idea is to have a palette with virtually every conceivable object a user would want just one click away from creation. That means if I click on the button marked ‘folder shortcut’, it will create an object that is pre-configured and only needs an image & target. If I click on the button marked ‘object with states’, it will create an object that has the mouse over, mouse away, mouse down, and mouse up states already added. If I click on the button marked ‘mask’, it will create an object with the appropriate image (a square one, not round) for use as a mask. If I click on the button marked ‘text object’, it will create a text object (instead of an image object which I have to change into a text object.)

 If I click on the button marked… well, here’s a video of what I mean: LINK

#3 Limited Builder Mode

I think DX needs a mode that bridges the gap between client and builder. A mode with training wheels, if you will.

So you’d have Client which is for end-users, Limited Builder Mode that’s for end-users turned new builders, and then pure no-holds-barred Builder Mode for users more familiar with the DX builder environment.

The limited builder mode would be more intuitive than the freestyle builder mode. This might be where you could implement #2.

It might also have some kind of central editor like ID mentioned. The editor could have quick access to only the most frequently modified properties of an object: name, parent, group, size, x/y coordinates, image (or text), visible, movement, activation—kinda like a revamped object navigator/object list. I imagine the information in the editor would change depending on which object you’re interacting with, e.g., if you click on an object, its information would show up in the editor and you can make quick changes without having to open up a properties window. I’ve actually made an object that does that, though, it works on mouse over instead of click, and it doesn’t work for child objects.

#4 An undo function

I can’t tell you how irksome it is to have to redo mistakenly deleted objects.

 

Smaller wishes:

#1 System tray & and other fixes

Fixing several of the bugs mentioned on the forums and bringing back the system tray.

#2 Expand the Script Wizard

We have script wizards for most activeX objects but I’d like to see one for regular objects. Take all the object/system callbacks listed in the Developer’s guide and list them in a script event wizard.

#3 Expand Auto Complete

DX auto completes Functions and Subs. Couldn’t it to also auto-complete Loops and Conditionals?

 

That’s all for now. A few weeks back I was doing some scripting and I thought "man, I wish DX could access such and such via script" … now I can’t remember what that was…    I really should've written it down.

I don't know anything about DesktopX except that it's a great, versatile program, but I'm thinking that somebody should track down Vad_M and get his input. He probably has a big wish list.

Include all the scripts that are available here at WC forums and sViz's Script Helper as 'templates'.

An advavnced DX player.

Low resource usage when using large animations.

Ability to import objects one by one or as a group from a dxtheme.

Yes. 

Damn!  That is awesome!!! 

Dear Zu, you are always encouraging me.    So I'm very calm and happy now!    

It's funny but I'm one of those strange people.   Just a little habit...

Still listening.  Thanks!

I think that there are several improvements that can be made which fall into 4 main categories:
1. Bugfixing
2. Additional functionality
3. Developer tools
4. Ease of use tools

1. Bugfixing
In addition to those already mentioned ...
Fix AX control bugs e.g. ...
Control.Border = False is broken on the DX Edit control
Sometimes controls don't appear on loading until they/their parent is moved
On crashing sometimes a duplicate of the last object in the navigator is created. This causes subsequent problems and crashing until manually removed from the theme2.ini file

2. Additional functionality
Some simple things could be added like improving tooltips
a. Allow a custom background
b. Allow custom font
c. Control over positioning relative to cursor
d. Maximum width/auto wrapping

3. Developer tools
Improve the Object Navigator
a. Ensure that it defaults to a sensible font so I don't have to manually uninstally fonts like Batang he to get it to display correctly / allow font choice to be saved globally
b. Make viewing more sensible - allow a tree view so children can be hidden unless I want to see them
c. Allow colour coding so I can quickly and easily find a specific object
d. Fix sorting - if I click to sort using a column how do I get it back to the default view without closing and reopening the Navigator
e. Allow me to exlude certain objects from export. In scripting objects are often created dynamically (e.g. calendars) and it would be easier to allow objects with certain names to be excluded when you "Select All"

4. Ease of use tools
I think that there have been a lot of valid points made above and I like the concept that you presented sViz, but I think we need to step back and make sure that this model is extensible.
Let me explain further ...
The key thing is that we have templates already. That is one of the key benefits of DX, in that you can load widgets and tweak them. These are our templates!

For example here is a perfectly functional calendar and here is the article explaining how to use it.
Whilst this is 5 years old it is still totally valid today.

Likewise, if you want weather then here is an equally old, but equally functional object.

What we need is an agreed standard for how we publish and utilise these within DesktopX.

Once we have this then what sViz proposed in the video is totally doable and extensible, because new "template" items can be added in a structured way (probably a tree/dropdown rather than icons because this is more flexible).

Users can create their own template item whether this is a complex set of objects, or a simple template for a text object or mask as per the video.

A standard implementation method is what will be required to sure that object names are not duplicated. Though clever use of programming (Object.Parent and Object.Name) we can ensure that all object names are relative and therefore it would be easier when cloning (using a method different to the current one).

Finally I believe we need a standard way to interact with the user. These template objects need to know where to get and put information in a structured way. Several years ago I proposed a CUI (which stood for common user information), which basically was an XML file when standard information was stored (Example of the draft).

OK, I think that's enough of a document for now.

I'd be delighted to assist in the development of this sort of thing. It's just the sort of thing that would encourage me to spend more time with DesktopX. However, what I (and I expect other developers) need is some reassurance that this sort of hing would be implemented and that the time spent working on this wouldn't be in vain.

Look forward to hearing what other people think.

M.

I just started with DesktopX, but one thing I'd like to see, is a way for DesktopX to use Themes that are marked "for this or that resolution ONLY". One in particular is the LCARS Theme by HG_Eliminator which can be found here.

I browsed the entire gallery, and you have no idea how many great-looking Themes I had to discard from consideration because they were only for certain resolutions that I cannot/do not wish to use.