Hi david
To browse traits used in a given class, we have this fourth switch next to instance / ? / class, called 'traits'. Clicking on it then lists in the next column all traits used in this class and the class itself. This additional column duplicates the switches instance / ? / class.
For classes using traits you can see methods coming from traits in italic, methods defined but not implemented in a trait in normal font when browsing the class and in blue when browsing the trait. You also see the hierarchy of the used traits in this 'trait column'.
But it's also possible to open this 'trait column' for classes that do not use any traits, this is very confusing. Also it's not nice to suddenly get five columns instead of four.
Yes!
My suggestions to better integrate traits is to show them below the classes using them directly in the class column, hierarchially sorted and marked either with an icon or with a colored label (eg. in blue). Like this we can get rid of this additional column and the additional 'trait' switch.
Would be cool.
The only problem I see with this change is that it might confuse people as traits are displayed along with all classes of a package/ class cat in the class column, although they might not be part of neither the package/class cat nor the class hierarchy.
What do you think, should I change it like this or not?
Give a try. I think that this is worth. I would like to rewrite a part of the collection hierarchy and use Nile so more traits. Stef
Cheers, David
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project