This was removed on request of Stef and I completely agree on this: for me it is time consuming to be forced to search for the selector in a sorted list when the selector is written/selected right in front of me.

Maybe I dont understand what you wrote - but if I understand you correctly OB had the same behavior as in Core and this was removed from OB on request of Stef? Again: when I have a method foo self sendMessage: myMessage with: text. self sendSecondMessage: myMessage. A) In Core: I'm able to browse the senders/implementors of all three selectors using the sorted list provided by the "Senders of..."/"Implementors of..." menu: #(foo, sendMessage:with:, sendSecondMessage:) where the methods selector (#foo) of the selected method is explicitly at the top. B) In Pharo (with OB): I can only check the senders/implementors of #foo which is limiting and makes it hard to search for s/i of the other messages sent from within the method body. => So I'm limited with Pharo(OB) compared to Standard browser in Core. Bye T. -- GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl. Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl