Experimental plug-in ready for test
Geoff Canyon
gcanyon at inspiredlogic.com
Wed May 15 04:16:00 EDT 2002
I've just placed ScriptBuddy onto a server. Feel free to download and check it out.d
ScriptBuddy is a hack, so it's not guaranteed to do the right thing all the time. You use it at your own risk, etc.
Specifically, there are ways to break it which I'll go into below.
What is it?
Script buddy is a plugin that serves as a holding place for scripts. It doesn't care about syntax, so you can store a script with errors or incomplete code and come back to it later. It's just one window that's able to easily store multiple objects' scripts, making it easy to open the full reference, etc., and return to scripts quickly.
How does it work?
When you put ScriptBuddy into the plugins folder and restart Revolution, you should be able to open it. I believe it will open as a palette, which is probably best. It can be resized to fairly large or fairly small. It contains only a button, a checkbox, and a list.
When you click the Get Script button, if there is a script window open, ScriptBuddy gets the formatted contents of the script and a reference to the object, stores them, and closes the script window. There is no theoretical limit to the number of scripts you can get this way.
The reference to the object is displayed in the list field, along with any other scripts you've gotten. If the Use Names checkbox is checked, then the reference is the long name of the control. If not, then it is the long id of the control.
Clicking on an object reference in the list opens the script for that object, restores it to the state it had when it was stored, and removes that entry from the list.
Why would I use it?
You might have several script windows open and want to work with just one. You might need to work with the scripts of several objects from different areas of your app, and need an easy way to keep track of them while you do. ScriptBuddy is a thought experiment, so maybe there is no practical use for you.
How can I break it?
ScriptBuddy isn't designed for use with Single-Handler view. It will eat scripts that way. Don't try it.
ScriptBuddy doesn't track name changes. If you get the script of something and then change its name, you'll have a hard time putting the script back in place.
ScriptBuddy probably won't hold values between launches.
ScriptBuddy is experimental. There is no error code. It could go horribly wrong and injure your dog. ;-) So be careful.
ScriptBuddy is at <http://www.poetickat.com/revdocs/>
--
regards,
Geoff Canyon
gcanyon at inspiredlogic.com
More information about the use-livecode
mailing list