I've managed to find the draft document I did many a moon ago. Obviously it's not up to date but I think most would still be valid. You can see the article here
Wow. And that was five years ago.
I ran into the CUI thing with one of your weather widgets; it seemed like a good idea, but I had no idea how to implement it. The document makes a lot of sense. As was stated in the old thread, CUI and AOI would definitely need a prompt, so the users can fill in the information easily. In your document you stated the CUI file should come with DX, which is a good idea, but what if exporting as a gadget? The file would need to be included with the final product since the targeted end-users would likely not have DX on their PC. If we were to have standard DX weather templates, for example, I'd imagine that would require a way to query whether or not the final creation was a gadget or widget so the script would know where to grab the CUI file from.
Most of us would rather see some new creativity within DesktopX, rather than a rehash of the same old objects as we've had (in the main) for the last 5 years. If it requires a more "simplistic" interface to bring some new blood and new ideas into the DesktopX community then I'm all for it.
Yup. Having both accessibility and new tools would be ideal, but I strongly believe accessibility is key to any further success with DesktopX otherwise most people just won't "get it" and it will remain a niche program.
We need support from Stardock, otherwise a future change could render all this work obsolete. We need positive involvement from all parties and a critical mass of users to adopt a "standard" otherwise there is no chance it will work.
Amen. Unless these templates, standards, and what-not are included with future versions of DX, there is no way the majority of users will know about them much less capitalize on them. Which is why the Wiki isn't working, the dozens of tutorials aren't reaching everyone, and the template/example widgets in the galleries majorly go unseen, unused.
We need maximum exposure. As it is, DX relies too much on the community for this. You can't expect the forums or galleries on WC to be the first stop for a new user looking for a headstart on using DX. I know I first looked in the Tutorial folder included with DX, at all the widgets included, and then in the User's Guide. If we're hoping to have any impact whatsoever in getting new users started with DX, this is where our efforts must be concentrated--within DX.
Reading over this thread, it all boils down to accessibility and power. Some would like more tools, more functions, more power. Others would just like for it to be easier to use.
Much more experienced DXers than I would know more about the kinds of powerful new functions DX needs, so accessibility and ease of use is my main focus with DX. It seems to me the root of this is in the interface. Think of any program and its interface is generally where you would gain access to all its functions--everything in plain view and a few clicks a way. DX has NO interface. It has a systray icon, r-click menus, properties windows, properties windows within properties windows, tabs, and tabs within tabs. DesktopX is a great program, quite revolutionary in my humble opinion, but it is time for reboot. While the concept of using nothing but the desktop (and individual properties windows) as the work environment has its perks, it falls short on so many levels. Such as the central/visual editor several people in this thread expressed a desire for. Such as having grids, guidlines, etc. Such as having a quick-creation object pallette.
DX already does a whole helluva lot; the problem is a whole helluva lot of people don't know how to make it do what it does.The only limitation should be the user's imagination, and not the complicated, frustrating process of realizing his or her idea. Give the user quick access to the tools at their disposal, and you simplify the creation process. Simplify the creation process, and you free up the user's time to learn new tricks and actually get creative.
An intuitive user interface seems like the most logical solution to the lack of accessibility, and I think Stardock should strongly consider implementing any new aids in this format. DX does not have to become an inside-the-box program but it does need a more developmentally-friendly environment. I think a set of DX Builder widgets, or one super-console with access to all the developer tools/aids mentioned here could be a step in the right direction.
I seem to be repeating myself.
Ima shut up now and get back to work. 
