FileContentsBrowser
Richard A. O'Keefe
ok at atlas.otago.ac.nz
Mon Apr 23 05:37:10 UTC 2001
Concerning the file class browser.
I suggest these changes.
PseudoClass>>comment
change "' has not been commented'"
to "' has not been commented in this file'"
PseudoClass>>definition
change "'There is no class definition for this class'"
to "'There is no class definition for ', self name, ' in this file'"
I've made these changes to my image, but what do other people think?
Depends on the use. I use it almost always in a context where I want to know
if a certain CS has negative implications on what's already there or how
hard it is to integrate certain changes (such as posts from the mailing
list) - in this case it's far more useful (and faster if when you scroll
over the classes in the CS) if you see that there's *no* change to a
definition (which translates into "okay, no serious problems with this
class"). For me, it's hardly ever useful to see if the existing definition
or all the methods that do already exist in the class - the FCB doesn't show
these either. Of course, there are other uses some of which might benefit
greatly from seeing the existing definition even if not present in the CS.
So if you need this feature why don't you add it?!
Because I only just learned about FCB and have already spent the first day
of the week reading and following up Squeak mail. I need to spend some time
on other things.
More information about the Squeak-dev
mailing list
|