Quote:
Originally posted by mmcgregor
Thanks for the script sugestion.
The issue with running the script externally was that this method of user input was supposed to be a simplistic way of providing a form interface to the scripting language so that dynamic decisions could be made as the script runs; I expect multiple modes of batch, scheduled batch, and interactive. Running a script externally means parsing a file or stdout text to understand what the user wanted to do. This complicates things, and at that point I'ld write a COM object in C# and expose an interface or wrap VBPro in an application that kicks it off with commandline macro defintion.
Also, the MessageBox/Input forms built into VBScript are way to limited!
|
For more complex or dynamic front-ends, a custom action or GUI wrapper that calls VBP is probably the way to go.
http://www.kinook.com/VisBuildPro/Ma...omptsample.htm
We've considered adding a way to create custom GUIs shown at build-time within VBP, but anything we created would probably be too limited compared to what's possible with the above methods.
Here are a few other possibilities:
http://blog.woodchop.com/2006/08/gooeyscript.html
http://www.toptensoftware.com/quickprompts/
http://www.google.com/search?q=vbscript%20gui