RB minutia

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

RB minutia

Bill Schwab-2
Blair,

I think you've already recorded this one, but, just in case: there is no
prompt before renaming a method from the PB.

One thing that I've missed for a while is a local definitions/references
command that does not require browsing the method of interest.  Usually it's
enough to browse def/refs globally and sort by package, though it would be
nice to have the ability to type a selector.  I encountered the same problem
with the RB though, because I wanted to rename a method in a particular
hierarchy, and it turns out to be implemented on only one branch - it would
have been nice to simply do something like this:

RefactoringSmalltalkSystem current
   renameMethod:( AbstractClass class compiledMethodAt:#methodToBeRenamed )
   inEnvironment:( BrowserEnvironment new forClasses:( Array
with:AbstractClass ) )
   caption:'Not quite right'

and not have to worry about whether I had gone high enough up in the
hierarchy.  Does that make sense?

Have a good one,

Bill

---
Wilhelm K. Schwab, Ph.D.
[hidden email]


Reply | Threaded
Open this post in threaded view
|

Re: RB minutia

Blair McGlashan
Bill

You wrote in message news:[hidden email]...
>
> I think you've already recorded this one, but, just in case: there is no
> prompt before renaming a method from the PB.
>
> One thing that I've missed for a while is a local definitions/references
> command that does not require browsing the method of interest.  Usually
it's
> enough to browse def/refs globally and sort by package, though it would be
> nice to have the ability to type a selector.  I encountered the same
problem
> with the RB though, because I wanted to rename a method in a particular
> hierarchy, and it turns out to be implemented on only one branch - it
would
> have been nice to simply do something like this:
>
> RefactoringSmalltalkSystem current
>    renameMethod:( AbstractClass class
compiledMethodAt:#methodToBeRenamed )
>    inEnvironment:( BrowserEnvironment new forClasses:( Array
> with:AbstractClass ) )
>    caption:'Not quite right'
>
> and not have to worry about whether I had gone high enough up in the
> hierarchy.  Does that make sense?

It does. I've wanted to do something similar a few times myself, and I
usually end up adding a dummy method at the appropriate point, performing
the refactoring, and then deleting the dummy. Its #763, but time will be
very tight for this release.

Regards

Blair