For all those who have ever had a grudge with the Workbench, this program's for you. Macintosh users are used to point-and-clicking and having it work every time (except on data files). Remember the time that you thought you could simply drag a program by its icon onto your hard drive, double-click it and have it work? There were always library files and assigns and startup-sequence entries. Until now. This program lets people with CLI experience make the Workbench idiot-proof for themselves and others. WBscript lets you place scripts into project icons. When you double-click the icon, the script is executed from a console device of your choice which has a current directory of the icon's location, or as a directory named the same thing as the project icon. In this way, when you write your scripts, you do not even have to supply path names to files and the script will still always find them. Why a put a script into a project icon, you ask? And how can it be associated with a directory full of stuff? There are several advantages to placing a script inside a .info file rather than a separate script file. Any icon will associate itself with a file or directory of the same name regardless of whether it is the proper type. A project icon will attach itself to a directory. When you drag it around, it will carry the entire drawer, but it will not allow you to run the program or open the drawer in the regular manner. If you had a program with some related files that you wanted to keep in the same directory but the program wants to find in your system directories (terminal programs for instance), you could transform its directory's drawer icon into a project icon and put the C.L.I. commands in there. The current directory of the script is whatever directory the icon is in so that your script can refer to items inside that directory without full path names. Now, you will be able to pick up the directory and move it wherever you want while carrying all the related files, but when you double click it will run the program. With a special tool type entry, you could freely change the name of the directory and not have it effect the execution of the script file. A possible application would be if you had a program that requires some assigns before it is run. Instead of having a separate script file, startup-sequence entry, or to type the commands every time, you can transform the program's tool icon into a project icon and put the assigns right in there. It is now one integrated package that when double clicked will run the program properly and when dragged will carry the icon, script, and program. Since the commands are true scripts, it is totally appropriate to use "if" statements. You can create documentation icons that aggressively determine and use whatever reading utility a person happens to have on their system. Of course, WBscript will also allow you to do things from the workbench which just weren't possible before. C.L.I.-only programs can be attached to icons and be able to be dragged with them. With IconX and Xicon, this was impossible because the icon was already attached to a script file. The script would move with the icon while leaving the items it referred to behind. A clever workbench user will be able to assemble packages that will make them seem to have programming ability. For instance, by putting the SuperView utility inside a directory with a bunch of pictures, you can run an entire slide-show by clicking the directory icon and copy the whole thing to your hard drive by dragging that same icon. People are likely to never even realize it is not a program they are running. You can put WBscript inside that directory and set the path to it so that people don't need to already have the program. I made a WBScript utility that will attach icons onto all files in a directory by simply dragging an icon to the drawer from Workbench and double-clicking it. When you closed the drawer and opened it, there laid out in neatly placed order were icons belonging to the previously invisible files. All I used that was not standard Amiga DOS was WBScript and LS, a versatile listing command with a NOT operator. You can probably figure out the rest. You can see WBscript's C.L.I. parameters by typing "wbscript" in a C.L.I. or shell. Operation should be pretty obvious for anyone who is already familiar with C.L.I. formats. You can change several things about an icon from there. If you already have a script file prepared, you can set the type of the icon to project and load the script into it and be in business with little work. In order to see the changes you've made from the C.L.I., you must remove it from workbench's view then reintroduce it by closing the drawer it resides in then reopening it. Now when you do an info on it, you will see the change. The script files can be created in any text editor and saved as a file temporarily. The script can then be transferred into the .info file by typing from a console: wbscript load