What sorts of features would you like to see in the 4.x series?
I would like to see templates of sort, perhaps a visual editor.
Take DashCode for example.
A system tray.
Scripting
[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 am still very new to desktopx, but one thing i would really like is better support for system tray on vista. And an updated media player with more features. Thats all that i can think of now.
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.
I see that I've missed some important things! As always...
What can I say? I have had many thoughts on this subject. But I forgot a lot of them during this time... However I'll try:
1. Fix for WMI control. Some WMI scripts doesn't work on Vista without hacking the System Security Settings through auxiliary functions...
2. Full access to Windows API to create more usefull performance meters and administrative desktop applications. It would be great to see support for Visual Basic 6.0. DesktopX will be incredible in this case!
3. Full access to ActiveX controls. In particular - to Windows Media Player 11 (in Vista). As well I found a lot of bugs in this area when have tried to work with ListView, TreeView, ImageList, etc... DesktopX stops working and requires a reboot from time to time.
4. Support for Windows 64bit...
5. Expand the possibility of scripted animation. At least for images that has frames stacked verticaly.
6. Add "minimize" or "hide/unhide" option to Object Navigator.
7. Please, fix a bug with fonts in the Script Editor.
That's all I remember right now.
P.S. How much monthes/years we will waiting for DX 4.x? Do I really have a chance to be alive and see this Great Day?
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!!! I use the object navigator constantly and it makes no sense that it doesn't have a minimize button.
Also, the keyboard shortcut for select all (ctrl+A) does not work in the Script Editor. It seems to me that above any new feature, it would be really nice to see some of the current features fixed and working properly.