Notepad++ + external scripts.

At the moment I think the hardest thing for me to do will be 'code block collapsing' that notepad++ does.
Notepad++ would have been my first choice for making a customized editor - but I'm not clever enough to work out how to do it..

This will be better though because I can deliberately interact with the theme directory and the objects within DesktopX as the editor will run as a desktopX object itself Gives me some ideas which would have been too difficult or impossible with Notepad++

Gotta tell Notepad ++ what you are editing so that it gets the right colors. Saving after you start helps, or if you are crazy like me I tell it what I want to be - it's under Language.

Cool Liz! You're taken care of then

I stumbled upon VbsEdit today. Nice set of features.

http://www.vbsedit.com

Nifty find!

I have an 'auto-complete list' and basic function 'help tooltip' mechanisms working nicely.
The current code highlighting is just the default Visual Basic support in the control, but adding more won't be very hard at all.

The 'window' is just a bunch of DesktopX objects and graphics, no animations but the buttons etc. all do what they are supposed to.

Interestingly the ActiveX control I've used has many functions I can't make use of as they are intended for proper Visual Basic interfacing - one in particular is controlling which lines are rendered, which I could use to create collapsible sections.

Also some apparent bugs in the control which I've had to script inelegant (but functional) workarounds for as I don't have source code (and wouldn't know how to edit it anyway).

To add:

• function 'jump list' (to jump to a Sub or Function) without having to scroll through the script via a drop list.
• rather than 'tabs' for each script, a treeview of DesktopX objects, clicking nodes to show the script.
• compiling a bunch of xml entries for various vbScript object models for the 'intellisense' - vbsEdit (mentioned by c242) will probably help me out there as it already has a comprehensive list.
• object variable typing - this is so if you create a variable to hold e.g. a FileSystemObject, the 'intellisense' will know to display FileSystemObject information correctly.

WIP-shot:

That's quite cool.

Nice work!

Duhyy....is there an english copy?