> On 19 Aug 2015, at 20:26, Dimitris Chloupis <kilon.al...@gmail.com> wrote: > > > > On Wed, Aug 19, 2015 at 5:51 PM Sean P. DeNigris <s...@clipperadams.com > <mailto:s...@clipperadams.com>> wrote: > kilon.alios wrote > > > For example, let's say your project has a class that implements a > generically-named method, like #asMorph. If you try to rename that method > via Refactoring, Pharo will try to rename all #asMorph methods, and update > all senders, in the entire system, not just yours. But if you scope the > browser first to your package or class, you can restrict the environment to > which the refactoring is applied > > This sounds useful indeed. Is just the browser aware of the scope or is also > the pharo environment aware of the scope too ? It would be nice if the scope > could expand to include multiple packages , or is this something left to > groups ?
no, you can select and then browse scoped : - multiple packages - groups (btw, current scoped button does not takes that into account) - a single class (you have to use the context menu on classes for it) it is really powerful :) Esteban >
