I just checked -- you are right, I got it backwards. A change set would be great. Is there a real reason to keep the OBMethodListBrowser? What is it good for?
Cheers, - on On Feb 9, 2009, at 16:12, David Röthlisberger wrote: > Hi Oscar, > >> If I enable halos and explore the morphs, I see that the first one >> has >> as its model an OBImplementorsBrowser, and the second an >> OBMethodListBrowser. Why not simply use the latter? I searched for >> references to both, but did not immediately see how to change the >> behaviour on <cmd>-m. > > I think it is the other way around: In the workspace you get the > OBMethodListBrowser > and in the class browser the OBImplementorsBrowser? > > The reason for this is that the workspace passes the request to the > SystemNavigation > class. After this class has gathered the set of messages to display, > it passes this > set to a method opening the so called message set browser which can > only reason about > a set of methods, not about whether these are senders or > implementors. That's why we > get a generic message list browser there but a dedicated > implementors browser in OB. > > So we need to change SystemNavigation to achieve the same result in > both scenarios. I > can propose a change set. > > David > > _______________________________________________ > 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
