Persistent Workspace

Lex Spoon lex at cc.gatech.edu
Thu Mar 4 17:01:03 UTC 2004


ducasse <ducasse at iam.unibe.ch> wrote:
> I completely agree. I did the same and I never use a workspace because 
> I can edit code
> anywhere anyway. Even at the end I just invoke Opener install which 
> call all the scripts so I can have multiple
> installations processes.

That wouldn't work for me, because my workspace usage involves a lot of
workspace variables.

I really would like a workspace that is connected to an instance of some
class, where "workspace variables" are the same as instance variables of
that class.  Or alternatively, a browser that keeps track of a prototype
instance of each class, so that I can do workspace-like things in it
without losing the data I've computed.


-Lex



More information about the Squeak-dev mailing list