David I would love to know when browsing a class if the method comes from a trait :)

Stef

On Sep 23, 2008, at 9:04 AM, Lukas Renggli wrote:

OB-Enhancements version 0.203

I am horrified with all these colored icons on methods. That's worse
than in the old browser with the button that had 8 different colors
depending on the state of the method.

- I don't want to see part of the "contents" of a method as an icon.
The super-icon is useless, it only hides valuable information (for
example that there is a sub-implementation). If I want to know if a
method calls super (and when) I need to look at the method anyway.

- The same is for abstract method icon. When browsing the
protocol/interface I don't need to know that. I am more interested if
any of the subclasses override it.

- The same for extension methods. I see that, because it is in a
different protocol and because its name is in italic (the same as with
the extension classes). I don't need yet another icon.

The only valuable thing for me as a developer is to know if there is a
super/sub implementation of a method. And maybe if there are halts
inside. The rest I can find out with one click or less, if necessary.
This would greatly improve the interface. The browser starts to be
really messy.

Furthermore I would like to define my own icons for classes, for
example Seaside component should have its own icon. So instead of
hardcoding this into OB itself why not asking the class for an icon,
as this is done in VW for example.

Cheers,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project



_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to