Yes it is a bit frustrating. For example the OBdebugger in the dev image does not have all the menu items and the problem is that this is always under stress that we get to notice that :)
Stef On Feb 7, 2009, at 12:44 PM, Oscar Nierstrasz wrote: > > Hi Folks, > > I am confused by the various method browsers in Pharo. > > If I <cmd>-m on (say) @ in a Workspace, then I get an "Implementors" > view with two panes, the top ones showing 6 implementors of @. If I > click on any implementation, I see the source code in the second pane > and that's all. > > Now, If I click on the "implementors" button I get a *new* > Implementors browser that looks exactly the same, but isn't. Now if I > click on one of the methods, I also get in addition to the source code > in the bottom pane, a nice *third* sliding panel on the top with all > the messages sent in that method. I can then conveniently browse > through the whole call tree. > > How come I only get the more powerful method browser by explicitly > clicking on "implementors" but not when I type <cmd>-m? > > 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. > > - on > > > _______________________________________________ > 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
