> As a remainder, this is what you can do from the search bar. Type: > ClassName (starts with uppercase, look up class definition) > #ClassName (look up references to ClassName) > methodName (starts with lowercase, look up implementors of methodName) > #methodName (look up senders of methodName) > - 'string' (look up for string in methods (not the same as look up in method > source, which is much slower))
There is another one if you have the refactoring tools loaded. If the expression contains a backquote it searches for parse tree patterns, e.g. `...@expr instVarNamed: `#string finds all the senders of #instVarNamed: that have a plain string-literal as its argument. > The search bar also works with completion, so it doubles as a useful launch > bar actually. The fact that completion works is quite accidental and should be improved :-) > Any idea welcomed Actually, Colin and I were discussing about removing the Mercury panel. We observed that almost nobody uses or knows how to use it. I personally never use it, I find other ways to navigate much more efficient and simpler to perform without the need of typing cryptographic sequences of characters :-) The mercury panel is highly extensible, so maybe it would make sense to move it into an externally maintained package? Lukas -- Lukas Renggli www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
