Re: Refactoring Wish List

[Greg Fenton]

There is one aspect of "changing/deleting class names" that is
not obvious:

  Version Control.

I wonder, should refactoring get implemented, whether work would
be done to try to integrate with VC (cvs, rcs, p4, ...)

Having a tool to rename and delete files won't be good enough
for some VC systems (e.g. "p4 integrate").

Just a thought,
greg_fenton.


=
Greg Fenton
[EMAIL PROTECTED]

__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

Re: Refactoring Wish List

[Bill Appelbe]

Hi
Just a suggestion to look at this.
I haven't a lot of time to examine the list, but a number of them are in
JRefactory (http://jrefactory.sourceforge.net/) which has on the "Requested 
Features" list to integrate to JDEE.

I haven't used JRefactory but came across it some time ago and 
bookmarked it.

Bill

At 18:22 02/12/2002 -0500, Nascif Abousalh-Neto wrote:

>So far we have: 
>
>1. Changing class name (and all references). 
>2. Changing names of any choosen class member - field, method (and all references) 
>3. Changing package for one or more classes with 'one click' (and all references) 
>4. Moving class to different package 
>5. Create factory method in place of constructor 
>6. Extract method from selected piece of code 
>7. Extract super class or interface for selected piece of code and set of fields 
>8. Deleting classes/methods/attributes 
>9. Copying classes into other packages 
>10.Copying methods/attributes into other classes 
>
>I would like to see some features from Transmogrify, which may not be necessarily 
>refactorings but are easy to implement once you have a refactoring framework (which 
>requires the complete syntax trees plus reference resolution) in place:
>
>11. Wrapping a block of code in a try/catch (exceptions needed extracted from the 
>signatures of the methods in the block)
>
>12. Finding out unsused variables/methods/classes 
>13. Finding out shadowed variables/methods 
>
>Maybe we should have a page somewhere and vote? A system like bugzilla to track 
>requirements/bugs and get user input on the most desirable ones would be nice.
>
>For a comprehensive list of Refactorings as documented by Martin Fowler, check 
>http://www.refactoring.com/catalog/index.html
>
>Regards, 
>Nascif 

RE: Refactoring Wish List

[Paul Kinnucan]

Sebastian Hauer writes:
 > Not exactly refactoring but unbelievably useful.
 > Find the usage of a variable or method name.
 >  
 > If JDEE or some other free emacs mode is able to provide this feature
 > please let me know.
 >  
 
Have you tried the JDEE's Find Expression command. It displays
every instance of an expression that it finds on the current
source path in a buffer. Clicking on an instance opens the
corresponding source file to the place where the expression
occurs. I use this feature to find every reference to a 
method or variable name. Of course, an intelligent find
method that differentiates between ClassA.method() and
ClassB.method() would be better and I hope that the JDEE
will evantually provide this capability.

- Paul

RE: Refactoring Wish List

[Sebastian Hauer]

Hi Paul,

> -Original Message-
> From: Paul Kinnucan [mailto:[EMAIL PROTECTED]] 
> Sent: Tuesday, December 03, 2002 10:55 AM
> To: Sebastian Hauer
> Cc: [EMAIL PROTECTED]
> Subject: RE: Refactoring Wish List
> 
> 
> Sebastian Hauer writes:
>  > Not exactly refactoring but unbelievably useful.
>  > Find the usage of a variable or method name.
>  >  
>  > If JDEE or some other free emacs mode is able to provide 
> this feature  > please let me know.  >  
>  
> Have you tried the JDEE's Find Expression command. It 
> displays every instance of an expression that it finds on the 
> current source path in a buffer. Clicking on an instance 

No I did not try this until now. But it does a simple "find /src -name
"*.java" -type f | xargs grep -i -n Expression" only something that I
did anyway from the command line. I have to admit having the file name
in the search buffer is nice though.

> method or variable name. Of course, an intelligent find
> method that differentiates between ClassA.method() and
> ClassB.method() would be better and I hope that the JDEE
> will evantually provide this capability.

Well yes this is more what I was looking for. I like JDE but I kind of
need this feature. All my co workers are already working on InteliJ IDEA
but I don't want to give up emacs so I had to install the shareware tool
xref which does a good job but is of cause not integrated with JDE and
some refactoring stuff takes unbelievably long compared to IDEA.

Sebastian