I think all this topic should be quite easy. It should be similar to OB "scope". All refactors like method rename affects everything if the scope is the default. If you want to affect only a class/package do a "Browse scoped" to a class/package. And then the refactors should only affect that. Of course, we should explain this somewhere in Pharo doc. I think this is quite easy and enough for most cases.
On Thu, Feb 21, 2013 at 6:45 AM, Goubier Thierry <thierry.goub...@cea.fr>wrote: > Le 20/02/2013 21:33, Benjamin a écrit : > >> On Feb 20, 2013, at 8:43 PM, stephane ducasse <stephane.duca...@free.fr >> <mailto:stephane.ducasse@free.**fr <stephane.duca...@free.fr>>> wrote: >> >> >>> On Feb 20, 2013, at 1:07 PM, Benjamin >>> <benjamin.vanryseghem.pharo@**gmail.com<benjamin.vanryseghem.ph...@gmail.com> >>> <mailto:benjamin.vanryseghem.**ph...@gmail.com<benjamin.vanryseghem.ph...@gmail.com>>> >>> wrote: >>> >>> There is actually no simple way to simply rename a method. >>>> We should maybe add one which keep track of the versions :) >>>> >>> >>> sure there is: >>> click on the method >>> in the text pane change the selector of the method and compile. >>> >> >> I am kind of aware of that :) >> >> But for a new comer, it's not obvious at all. >> And usually they first look in the menu and click on the first entry >> "matching" the need >> >> Ben >> > > What about restricting the rename to the current package or class? With, > say, a box to tick to go system wide? > > (And a nice GUI, moose-like, showing on a color map how much of the system > the rename will impact :)) > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des Systèmes Temps Réel Embarqués > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > > -- Mariano http://marianopeck.wordpress.com
