Here is these change log of various DesktopX versions.

Version 2.4 to 3.0: March 2005

• Scripting API to control system volume.
• More text features to deal with multi-line and limited size text.
• Scripting API to read and write the system clipboard.
• New software component called Widget Manager to better organize and access widgets.
• User mode and Builder desktop modes now separated into different runtime components.
• Scripting API to easily monitor the CPU usage.
• Scriptable plug-in support.
• Scriptable email notification plug-in.
• Centralized scripting support. One single script can control other objects, handle their events.
• Widgets cache versioning. New versions of loaded widgets will automatically clear and update the cache.
• Custom widget preferences support.
• Major UI simplification and improvements.
• Much simpler bitmap margins/tile/stretch configuration.
• Scriptable animations -- access a particular frame in a bitstrip from script.
• Major ActiveX performance and usability improvements. ActiveX controls can even be made transparent. Object.SetFocus on ActiveX objects now correctly passes keyboard focus to the control.
• Rewritten the widget and gadget reposition code to ensure content is inside screen.
• New "DesktopX Welcome" Component to access all components of DesktopX.
• New autorun/restoring behaviour when leaving DX running and closing Windows.
• Stable WMI support. WMI let you access a wide set of Windows services.
• Lots of new scripting features to access and modify objects properties.
• Fixed systray and taskbar icons get invisible.
• Fixed Tasbkar object transparent labels.
• Added "Open desktop data folder" button to DXBuilder UI.
• Fixed the proliferation of .dxscript files while editing objects. The current theme folder is purged automatically from unused files.
• Fixed Set Target for URLs in User mode.
• Fixed Widget preferences breaking drawing plugins.
• Fixed some crash bug WB incompatibility.
• Widgets can have custom preferences dialogs defined from the script.
• Objects in user mode contain a "remove" and when applicable "set target" context menu.
• UI Threading - scripts are synchronized with their associated object (i.e. no more timing issues about when a script starts to execute when an object is created)
• Objects can be created from scripts.
• Scripts can create custom states for objects on the fly.