Script command

When you run a script, it now uses a script command. Its an interesting command as it uses a new session object to run the script and, by extending the UI class, uses itself as the user interface object while the script is running.

The script command normally produces no display unless there is an error. Then it lists the commands which were run, and the error produced by the last command that was run.

Script is an invisible command--you will not find it via the help command.

Another nice thing is that clients can now pass documents together with the command line, via the portal, user interface object and session to the active evaluator. Indeed, this is now what happens when you run a script. And this facility opens the doors for things like editing documents and tables. Its been on the todo list for a while, but was never an immediate requirement.

Perhaps tomorrow I can work on Swing like I had planned. Of course the door is now wide open for implementing RMI, and that would give a better testing environment. But after getting the swing client caught up with the text client, which shouldn't be much, I need to focus again on descriptors so I can start adding some commands. There really isn't a lot you can do with AW3 right now except create cabinets, journal and set access restrictions. :-(

Bill