You might know I'm trying my hand at a script editor specifically for DesktopX.

I've extended my plan to a general DesktopX 'editor' which can help in the creation of DesktopX objects etc.

I've already planned out some features - some of which do duplicate what DesktopX already provides through it's properties window - but hopefully makes them more accessible and flexible. I've also asked Stardock support for some updates to DesktopX which would make this progress really nicely - but just fingers crossed for that right?)

I've come now to considering how DesktopX 'attaches' scripts to objects. This attachment means that script 'space' receives the events of the object (like click/move etc.) first. Then there is the concept of the Ex functions which lets parents of objects receive the events next from their children.

I'm thinking of taking that further and decoupling the idea of scripts being attached to objects, and instead make them their own 'element'.
To facilitate object events there would be an option to 'pipe' the events to whichever script 'element' you like.

The above would let you have e.g. a main central script for handling *every* object in your widget/theme, or a seperate script just for events, or even smaller sub 'scriptlets' for specialist functions or behaviours. Essentially we could then work on scriptlets which can be shared amongst developers and used in DesktopX a little bit like plugins to provide specific behaviours/properties to an object (or set of objects).

Any thoughts or suggestions?

P.S. Not so much looking for 'how would you do this?' comments - I know a way to do it as I've described Just looking for different suggestions or additional ideas for how you see scripting working in DesktopX.

And here's a picture of my object browser so far (to replace the object list DesktopX already has)