I like the idea, but not these names, they are way to generic. 
Especially the 'knows' is really too much, and it is also a form of 
sharing (it just has a different scope). So maybe something like this?

>> Morph
>>     subclass: #MyMorph
>>     has: ' myTarget lastTime '
>>     instancesShare: ' CloseBoxImage '
>>     poolsShare: ' Colors '
>>     category: 'Morphic-Samples'!


On Wednesday, November 27, 2002, at 10:31 AM, Stephane Ducasse wrote:

> The more I play with the idea the more I like it
>
>> Morph
>>     subclass: #MyMorph
>>     has: ' myTarget lastTime '
>>     share: ' CloseBoxImage '
>>     knows: ' Colors '
>>     category: 'Morphic-Samples'!
>
> Have you any experience related to possible problems student could 
> have.
>
>
> On mardi, novembre 26, 2002, at 11:14  pm, Alejandro F. Reimondo wrote:
>
>> Hi
>>
>> I am not a teacher, but... I would love to rename:
>>     instanceVariables ---> parts (of an instance)
>>     classVariables    ---> parts (of the class)
>>     sharedVariables ---> shared objects
>>
>> Because they are not "variables", they are
>>  only "names" of well known objects.
>> I think they are not variables, because the named
>>  object is replaced entirely by other (like a focus change)
>>  and do not change "in-memory" as occurs in memory
>>  dependent languages (assignment is a name change,
>>  not a variable overwrite... it is a very important thing
>>  to teach).
>>
>> Variables refer to a position, an area that can change contents.
>> So, you can associate a type/size to a variable.
>> Objects does not know about their "material" support,
>>  they only know another named objects and names
>>  are used to focus during message send.
>>
>> A class definition message can be specified as:
>>
>> Morph
>>     subclass: #MyMorph
>>      parts: ' myTarget lastTime '
>>      share: ' CloseBoxImage '
>>      pools: ' Colors '
>>      category: 'Morphic-Samples'!
>>
>> MyMorph class parts: ' defaultInstance '!
>>
>> or...
>>
>>
>>
>> MyMorph class parts: ' defaultInstance '!
>>
>> We have part names (aka internal collaborator),
>>  and global names in a rich set of global scopes
>>  (local context names, instance parts names,
>>  class-scope shared names, global names,
>>   pool names, outerScope names [in foreign
>>   namespace], ... ).
>> Always names, only names
>>
>> cheers,
>> Ale.
>>
>>
>> ----- Original Message -----
>> From: "Stephane Ducasse" <ducasse at iam.unibe.ch>
>> To: "squeak dev" <squeak-dev at lists.squeakfoundation.org>
>> Sent: Tuesday, November 26, 2002 6:34 PM
>> Subject: A big teacher wish
>>
>>
>>> Hi
>>>
>>> all this is something that I really appreciated in VW7.0 and I think
>>> that it would
>>> save a lot of energy to teachers and to newbies. I would loved to
>>> rename classVariables
>>> as sharedVariables (what they are in fact). This way we could say
>>> instanceVariables, class instance variable and shared variables.
>>>
>>> I would like to know the opinion of the community on that and idea 
>>> how
>>> to go there.
>>>
>>> Stef
>>>
>>>
>>> Dr. Stéphane DUCASSE (ducasse at iam.unibe.ch)
>>> http://www.iam.unibe.ch/~ducasse/
>>>   "if you knew today was your last day on earth, what would you do
>>>   different? ... especially if, by doing something different, today
>>>   might not be your last day on earth" Calvin&Hobbes
>>>
>>>
>>>
>>
>>
>>
> Dr. Stéphane DUCASSE (ducasse at iam.unibe.ch) 
> http://www.iam.unibe.ch/~ducasse/
>  "if you knew today was your last day on earth, what would you do
>  different? ... especially if, by doing something different, today
>  might not be your last day on earth" Calvin&Hobbes
>
>
>
Roel Wuyts                                                   Software 
Composition Group
roel.wuyts at iam.unibe.ch                       University of Bern, 
Switzerland
http://www.iam.unibe.ch/~wuyts/
Board Member of the European Smalltalk User Group: www.esug.org