I would like to point out that writing comments for the class definition is not a poor job to be done since it can very easily be read clicking in the '?' button of the majority of the browsers. I dare to write that from a quality POV we should put as an "issue" for the release of version 1.0 that all comments in the core image must be written and verified. It is a little scary when one is browsing a class and finds a "THIS CLASS HAS NO COMMENT!" or a "A ____ is xxxxxxxxx."... BTW, an interesting behaviour (at least to my expectations) happens in the core image (where I believe the ST-80 look for browser is the default): if you click in a class that has a "...xxxx." in the comment the bottom pane shows the "THIS CLASS HAS NO COMMENT!" in red. I surmise a reasonable machinery has been put on this pane to be able to display such message, isn't it? -- Cesar Rabak Em 03/12/2009 14:42, Stéphane Ducasse <stephane.ducasse@inria.fr> escreveu: On Dec 3, 2009, at 5:35 PM, Lukas Renggli wrote:
Hi Stef
I hope that the trip was good.
Yep, just arrived home.
Reboot :)
this was to get the comment below the class definition This is in the preferences at least on my image (rc1.0).
That split class-definition/class-comment view is only available in the ST-80 browser. I think that would be difficult to implement in OB.
ok too bad because nicolas made me think that we are doing a poor job at pushing people to write comments since nobody can easily read them.
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project