DesktopX can already use Flash files right now. There are Flash widgets available here on WinCustomize.
People say WindowBlinds is a resource hog even though that's obviously not true. In what way were you using DesktopX that made it feel like a resource hog? On its own, even DesktopX 2 uses relatively little memory, CPU, or other resources.
I don't think you'd like the .NET framework support as much as you might think. We seriously considered this because the long term plan is to have XAML be the underlying mark up language and see most widgets written in C# or VB.net. But that woudl require every user to download around 25 megs of libraries first (the .net libraries) which we don't think most people would put up with.
The scripting features are already pretty mature. I mean, it includes a built in editor with intellisense.
I'm not sure what Longhorn emulation woudl entail.
As for 3D capabilities, I'm not sure what you mean there either. Down the line, we do want to support .x (Direct3D's native model format) but that will have to wait until Avalon is available in the OS.
This is what we're working for.
The goal in DesktopX 3.x is to allow people to do it all via script if they choose. Even object creation:
myObject = DesktopX.CreateObject("ObjectIDHere");myObject.Class = "URL";myObject.ShortCut = https://www.stardock.com;
Things of that nature is what we're hoping to do. How much will be in 3.0 we're not sure. Certainly for the most common types of uses we plan to make that all doable in script (object creation/deletion).
There are many great features available to you once you register, including:
Sign in or Create Account
Thank you! Please check your email for a confirmation link. Once confirmed, you can look forward to receiving exclusive specials and announcements direct from Stardock.
Need to unsubscribe?