Hi Rich!

Trying to give concrete useful (possibly) advice, here are a few things:

	- In Gjallar we have Q2Console and Q2CodeHolder that enable "silent"
running of Squeak code and tries hard to do autocorrections etc as the
live Squeak env does. There are quite a number of messages that needs to
be handled in order to cover all bases, like autoadding local varnames
not declared etc. etc.

	- A useful pattern is to use blocks for "scripts" like: '[:customer
:invoive | ', script, ']' and then call it with the arguments and
explain to the user that he should use "customer" and "invoice" to refer
to those (or whatever) objects in the script. This way you get a more
clearly defined scope instead of just running the script "inside" a
given domain object (and thus expose all instvars etc).

Then of course there are tons of nifty things you can do with actually
building classes dynamically etc. :) And another trick is to subclass
Parser and friends and hook into for example the logic for binding
variables and so on. In my Namespaces implementation on SM there is a
bit of such code that deals with resolving globals for example.

regards, Göran