"Chris Becker" <chb99 at msn.com> wrote:
> How about this alternative for direct module references ...
> 
> ellipse := ModuleReference morphic core basic EllipseMorph new.
> 
> Even without an understanding of the underlying classes you get a good idea
> of what is going on.
> 

I don't know if it's been mentioned, but if we map messages to variable
names we are using messages in a different than normal.  For example, I
doubt you'll be able to browse to some class and see either "Morphic" or
"morphic" in the list of messages that are available.  For this reason
alone, I'd prefer  having a separate syntax for qualifying a name
lookup.

Note, you would still be able to talk to the module objects if you want
to.  You'd just use regular messages of the kind that will show up in a
browser, e.g.:

	Modules @ #Morphic @ #Core @ #Basic @ #EllipseMorph

Now you can look up #@ and see what is happening, where before you had
to lookup up #doesNotUnderstand:.


-Lex