Bert wrote:

> Missing class comments are indeed a problem. However, code  
> documentation generally is deemed less necessary, since Smalltalk  
> itself is rather verbose compared to other programming languages. In  
> addition, unit tests are seen as a good way to both document and  
> verify behavior. Like, in EventTest, you see many examples of how you  
> can use events.

Ok, rant over, it was trivial and does exactly what I want. Is there some
way to know there is a test class or does one rely on a naming convention
like System-Object Events-Tests in this case.

> But the most important thing for a Smalltalk novice is to learn how  
> to use the coding tools to explore the system. Senders, implementors,  
> inst var refs, class refs etc. are just a key-stroke away and help  
> you to get to know everything.

I am getting there.

> Btw, it would be nice if you stop sending HTML mails to the list - we  
> prefer plain text.

I will try and remember

Thank you for the help Bert.

- Bob -


*** Confidentiality Notice *** Proprietary/Confidential
Information belonging to CGI Group Inc. and its affiliates
may be contained in this message. If you are not a recipient
indicated or intended in this message (or responsible for
delivery of this message to such person), or you think for
any reason that this message may have been addressed to you
in error, you may not use or copy or deliver this message
to anyone else.  In such case, you should destroy this
message and are asked to notify the sender by reply email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20051109/58016dcc/attachment.htm