Frequently Asked Questions

Q	How do I get drag-and-drop to work?
A	Save your script as a Scriptlet - scriptlets are automatically drag-and-droppable. Make sure you have version 1.1.1 or later - the 1.1 beta had a bug which prevented drag-and-drop from showing up in the argument list.

Q	How do I make a Scriptlet?
A	Just select "Save As" from the "File" menu, and choose "Scriptlet" from the popup menu. Then save normally. Your script will be saved as a Scriptlet.

Q	What are Scriptlets good for?
A	As self-contained programs, you can distribute them to people who don't have ScriptGUI. But their real value is because they are "droppable" - you can drag and drop files and folders on them. Dropped files (and folders) appear as input arguments to the script.

Q	How is ScriptGUI different from DropScript?
A	DropScript doesn't show you the output of your scripts. ScriptGUI does. What's more, ScriptGUI handles STDIN correctly as well, so you can interact with the user.

Q	I can rename my scripts filename.command and they'll run in Terminal. Why is ScriptGUI better?
A	Running scripts from the Terminal in this way doesn't allow you to drag and drop files to have them interpreted as script arguments. Plus, combining the edit and run environments makes it pretty easy to test and debug scripts.

Q	Does ScriptGUI run on Mac OS 9?
A	No. ScriptGUI is written for Mac OS X only. This is primarily because OS X offers strong scripting support as part of the underlying UNIX operating system. I have no plans to support Mac OS 9.

Q	What about other OSs?
A	Although it would be possible to port ScriptGUI to other Unix-derived operating systems, I don't have the resources to do it at this time.