Lex,
My PersistentWorkspace lives as a Text on disk. This makes it easy to move 
it from one image to another.

A class also lives in disk (in a changes file or something) and can easily 
be filed into another image.

A workspace variable is like an instance (or class) variable. I guess it 
would be easy to store its specification on disk. What would be stored 
would be the name of a slot, not its value.

Values in a Workspace could be saved with e.g., storeOn: and read with 
readFrom: This _could_ be done i a PersistentWorkspace, but not in a class. 
Is that what you mean?

--Trygve

At 05.03.2004 10:39, you wrote:
>Lex Spoon wrote:
>
>>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.
>
>Lex,
>could you use class variables instead?
>Cheers,
>Wolfgang
>
>>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
>
>
>
>


-- 

Trygve Reenskaug      mailto: trygver at ifi.uio.no
Morgedalsvn. 5A       http://heim.ifi.uio.no/~trygver
N-0378 Oslo           Tel: (+47) 22 49 57 27
Norway