I think that, if it is technically possible (and I think it is, but may be I'm wrong), it is better to have VBScript (or an alternative) embedded in an AHK script, so if the script is compiled it will be "auto sufficent", say the integrated VBScript script will be executed as it was a "native" AHK script (I hope I am understandable and that it is possible !!!).
If it is your intent to add things such as ActiveX/OLE/COM, would not this be already what VBScript and AutoIt are offering?
May be it is usefull to say that :
1) Concerning AutoIt, the ActiveX DLL brings the ability
to other languages to use AutoIt commands, witch is probably of a very little use for the AHK users, as the two softwares have many common points.
I think that the AutoIt DLL don't give the ability (may be I'm wrong) to AutoIt programmers to call external (script) languages, nor to execute internally VBScript or VBA code, for example.
But may be this way can be studied, as it can be a good thing to be able to call AHK commands from VBScript or others programming environements witch supports ActiveX/COM ???
2) Concerning VBScript, it permits to use ActiveX/OLE/COM, so for example to execute VBA code, and so to control external apps like MS Office or other ActiveX/COM compliant apps, and I think it is one of the most important reasons (in my mind) to use VBScript embedded in AHK scripts : to be able to have "total" control over Excel and Word (standard softwares), for instance, from AHK.
There are a lot of VBA code examples to be able to develop automation procedures for Excel and Word.
It would give the possibility to send variables values to fill a word document/form or an Excel spreedsheet, for example, even if it is closed (ActiveX/COM/ADO) !!!
For example :
How To Use ADO with Excel Data from Visual Basic or VBAOr in the french Web site of
frederic sigonneau, button "VBA Excel" and then the "ADO et techniques de travail avec des classeurs fermés" link (ADO and techniques to work with closed workbooks), you can see (there are some example in english) how to read and write closed Excel workbooks with VBA and ADO.
There a probably a lot of other examples in the usenet group "microsoft.public.excel.programming", in witch you can search with
Google GroupsOf course we can already control Word or Excel from AHK, but the possibilities of control would be very much important and powerfull this way.
So, Chris, if you can (and want of course) integrate VBScript to AHK, may be you would not "have to" develop an ActiveX/COM/ADO interface, as it is already built in VBScript (may be I'm wrong, I don't know).
But in any case, which was already carried out in AHK is superb !!! A extraordinary work !!! Thanks Chris for the beautifull job.
Edit :
1) The target audience for AutoHotkey's missions are not programmers. I realize that you don't have to be a programmer to use something like VBScript, but you have to be close.
May be, but a forum can be the ideal place to share knowledge... When I see a Lazslo's script, I know there will be some (a lot of !!!) time before I can understand how it works, but it's the way to progress.
2) A lack of experience on my part, which means a steeper learning curve and more chance of making design mistakes.
A way for you to progress !!!! And (at least for me), there isn't any emergency (Aren't we in the "Wish List" forum, and not in the "Then, Chris, you can't go more quickly ?" forum ? (Joke ...

))