Visual Age Java Refactoring Browser

IBM has a feature request to add some sort of refactoring capability to VisualAge, similar to the various refactoring tools for Java (RefactoringBrowserForJava) or the RefactoringBrowser for Smalltalk.

#61 http://service5.boulder.ibm.com:8080/servlet/reqServlet3?feature=61 is: 

 Title:	 RefactoringBrowserForJava
 Product:	VisualAge for Java
 Component:	Integrated Development Environment (IDE
 Description:	There is an excellent book about java refactoring by
		MartinFowler. It would be great if at least some of the 
		refactorings can be supported by VisualAge for JavaIde.  Ex. 
		rename field, rename method, rename class, move field, move 
		method, self encapsulate field, inline method, extract
		method... 
 Platform(s):	All-Platforms
 Symptom(s):	Capability/Function, Usability
 Entered:	Thu Sep 30 14:57:23 MDT 1999 by AM
If you would like to see this feature added I would suggest you go to the request and vote for it. You will have to register, but it is free. As of March 22nd 2000 there are 85 votes for this feature. 

 IBM Status:  Wed Nov 10 15:39:15 MST 1999  
  User clarification - IBM is unable to respond to the request as defined. The
 request may not be considered further by IBM until it has been revised and
 clarified. See notes below for details of required information. 


  Can you help us prioritize the refactoring that we should do. It is not
 feasible to implement the entire book. ie: rename field, rename method, rename
 class, move field, move method, self encapsulate field, inline method, extract
 method... What are the five or ten most important. Thanks
So what are the five or ten most important refactorings when RefactoringInJava?

WikiMultipleVote

Note: max of 10 votes per voter since IBM is asking for 10 most important. Adding a new refactoring and voting for it only counts as one vote.

The page numbers are from MartinFowler 's book RefactoringImprovingTheDesignOfExistingCode

[CategoryRefactoringBrowser]

IMHO, this may be the wrong attitude. We say we shouldn't haggle with customers, yet here we are as customers, haggling. I suggest that either each refactoring is worth defending on its own merits, or it isn't. If you accept that, then instead of haggling over a top 10, we should be raising feature requests for each of the most important refactorings.

On the other hand, perhaps there is more value in AutomatedRefactorings? if there are lots of them, so perhaps starting with a top 10 is a good thing. On the other other hand, breaking down our request into smaller chunks may make it easier for IBM to chew through it.

--BenAveling

As of 7/19/00 this request was in seventh place.
I think most of these could be done, in some form, using the IDE Tools facilities already provided by the environment. Perhaps some of us could get at least a demo going, and then point the IBM folks at *that*. Or even offer that to the VisualAgeJava community as an independent offering. -- TomStambaugh
You may get better results by asking for these features from Instantiations, Inc. http://www.instantiations.com They make VAAssist, an IDE addon for VisualAge for Java. One of its features is the ability to move methods via DragAndDrop. They are very responsive to feature requests. --AveryRegier
Instantiations have done it - see http://www.instantiations.com/alchemy/ --ChanningWalton

Alchemy was the code name for jFactor - see http://www.instantiations.com/jfactor --DanRubel? (mailto:jfactor-support@instantiations.com)

EditText of this page (last edited March 20, 2001)
FindPage by browsing or searching

This page mirrored in WikiPagesAboutRefactoring as of July 17, 2004