Re: Refactoring wishlist

On Tue, Sep 20, 2011 at 10:02 PM, Joshua Kerievsky
<[email protected]> wrote:
> On Tue, Sep 20, 2011 at 9:59 PM, Adam Sroka <[email protected]> wrote:
>
>> IntelliJ has both the safe delete and a usable implementation of extract
>> class that allows you to chose methods including changing their visibility
>> on the fly. I forgot the Eclipse didn't have these. They are useful.
>>
>
> The Eclipse Extract Class works, but only extracts using one or more fields.
>  Then you need to do Move Method to get methods into the extracted class --
> not a terrible pain, but extracting some fields/methods in one shot would be
> sweet.
>
> Compose method sounds like an intriguing idea, but I fear that it would be
>> an example of what I was talking about – I wouldn't think to use it until I
>> was half way done doing it myself. But, maybe that is just me. Perhaps I
>> don't think as many steps ahead as some folks do when refactoring.
>>
>
> I don't write long methods but our clients do!   I wonder if Compose Method
> would help them more rapidly break up their Long Methods with less pain.
>  OTOH, producing good Composed Method takes thought and time and some tricks
> around where and how you extract methods.
>

That's a good point. I am thinking about this in terms of my usual
flow, but I could see how in legacy code some automation to help you
break up big chunks could be helpful.


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/refactoring/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/refactoring/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/