VisualDialogScripts [VDS] was used to write programs that can work in all versions of Rhino. These programs do not use the Rhinoceros SDK or, for most parts, do not use RhinoVisualBasic [RVB]. A Matrix of Plug-ins for any Rhino Version was started back in 1.1 days before visual basic was introduced to Rhino. There are good points and bad points about external plug-ins. The bad part is they are programs that run ontop of the host program. This means they can have focus over the host program. I have tried to do the best I can to send focus back to Rhino, but you may find the dialog having focus when you want Rhino to have the focus. Once you get used to it the problem vanishes. Because there might be a dialog element above all other application you can re-arrange the location or finish the scripted process before opening another application. As an example, Use the iconize button before switching to another application so the program iconizes with the Rhino program.
The good parts about external scripts are you can add new options to dialogs and even make dialogs that are not native to the host program. A program that looks at another program from the outside has the ability to manage a programs dialogs by location, size and even close them automatically if desired. This is why Automate was developed, to close dialogs that prevented scripts from continuing due to a button on a dialog that needed clicking. External scripting means you can design scripts independent of the host program. No need to worry about the SDK changing or internal methods changing between versions.
Some of my programs are experimental. The dialog design [GUI] varies allot with different programs. My feelings are the host program has a large work screen. The dialogs are Non-modal and share real estate space, therefore need to be as small and compact as possible. Another area is the usage of buttons or icons. By icons, I mean simple color shapes, small and click-able without any text. These icons can have a tooltip popup and a different color to indicate the mode or settings. I am sure there are other script designers using the same principal. As a reference, look at SliderTools and Tracer compared to a full button dialog and the screen space needed to perform the same operations.
The matrix of programs I have created uses its own language to communicate with different versions of Rhino with aliases. The aliases used are required however to run any of the programs found in this web site. There is an extensive use of data file and ini files to save settings. These files can be used by other applications and in scripts. There is allot going on in all the programs here. They are not simple command additions, but are a subsystem that requires AutoMate to be running whenever you want to use one of the module dialogs. AutoMate can be hidden and running through the Windows Task bar if you want. Please read the introductions about the programs before downloading and make sure you install the aliases before you use them. If you have any problems with installing the aliases, then make sure you backup your Rhino.ini file first and back up your alias list with Rhino before installing any of the programs found here.
A few things changed between Rhino 3 SR 2 and SR 3. I decided not to support older versions of service releases. I do not have the band width to manage all the changes. If your a current user of the MatrixX set of modules, please download the files with the asterisk...
Have fun and enjoy !
Doug Jones