Richard Staehli <rastaehli at mac.com> wrote:
> This mechanism is too complex, wastes time with rewriting and renaming, 
> fills up the change set with lots of useless changes, and sometimes 
> results in obsolete classes hanging around.  Anyone care to suggest a 
> better approach, particularly if it is easy to implement in our 
> prototype?  Since our component architecture must keep track of which 
> components are active and support binding, we don't need Smalltalk to 
> allocate a global name at all.  Ideally, we could create a read a class 
> from a stream just like any other object, without assuming that it is a 
> change to the code in the image.

You ought to look into extending an existing tool like Monticello; such
tools should already be used to the idea of manipulating a class that is
not currently installed in the running image.

There's also PackageBrowser in standard Squeak, which has some support
for that kind of thing.

-Lex