User talk:Sheng yi: Difference between revisions
No edit summary |
No edit summary |
||
Line 67: | Line 67: | ||
=== Example of using Ruby refactoring tools in Eclipse === | === Example of using Ruby refactoring tools in Eclipse === | ||
rename: | rename: | ||
{{multiple image | |||
| width = 100 | |||
| footer = Two cards used by football referees | |||
| image1 = r00.jpg | |||
| alt1 = Yellow cartouche | |||
| caption1 = Caution | |||
| image2 = r01.jpg | |||
| alt2 = Red cartouche | |||
| caption2 = Ejection | |||
| image3 = r02.jpg | |||
| alt3 = Red cartouche | |||
| caption3 = Ejection | |||
| image4 = r04.jpg | |||
| alt4 = Red cartouche | |||
| caption4 = Ejection | |||
| image5 = r05.jpg | |||
| alt5 = Red cartouche | |||
| caption5 = Ejection | |||
}} | |||
[[Image:r00.jpg]] | [[Image:r00.jpg]] | ||
[[Image:r01.jpg]] | [[Image:r01.jpg]] |
Revision as of 02:21, 6 September 2009
What is code refactoring
According to the famous book "Refactoring: Improving the Design of Existing Code " by Martin Fowler: Refactoring is the process of applying behavior-preserving transformations to a program with the objective of improving the program’s design. Intuitively people refer to code refactoring as "cleaning it up".
Motivation of refactoring
Refactoring is very useful for software engineer to maintain the quality of their code in different environment. In fact, no software can be guaranteed to be perfect when it is first developed. Usually when the source code is applied to different customer needs, we want to improve the inner-structure without modify the external behavior. The ability to refactor your code takes the pressure off the design phase of software development. Refactoring gives you the ability to change the design of the code at a later stage. This means that you don’t have to get the design absolutely right before you write any code. You can get a rough design worked out, code it up and then if (when) you spot a better design you can refactor your code towards the better design.
List of main refactoring
In the following we list some popular refactoring to specify how refactoring transform the code. For more detail information, the reader please refer to the section 2.1.2 of the thesis of Thomas Corbat[1]. [1] provide Ruby example for each refactoring this list.
1. Merge Class Parts |
2. Convert Local Variable to Field |
3. Encapsulate Field |
4. Extract Method |
5. Inline Class |
6. Inline Method |
7. Move Field |
8. Move Method |
9. Rename Class |
10. Rename Field |
11. Rename Local Variable |
12. Rename Method |
13. Replace Temporary Variable with Query |
14. Split Temporary Variable |
Some Ruby Example of refactoring
wait for Julian
Some Java Example of refactoring
wait for Julian
Refactoring support for Current Ruby IDE
This the following table we summary the current ruby IDE and their refactoring support situation.
Current Ruby IDE | Refactoring Support (Y/N) |
ActiveState Komodo | N |
NetBeans | N |
Arachno Ruby | N |
FreeRIDE | N |
Mondrian Ruby IDE | N |
Ruby in Steel | N |
RubyMine | Y |
Eclipse (Aptana) | Y |
Example of using Ruby refactoring tools in Eclipse
rename: Template:Multiple image
Example of using Java refactoring tools in Eclipse
Ruby vs Java in terms of refactoring
References
[1] Thomas Corbat, Lukas Felber, Mirko Stocker Refactoring Support for the Eclipse Ruby Development Tools, Diploma Thesis, HSR University of Applied Sciences Rapperswil Institute for Software
[2] code refactoring wiki, http://en.wikipedia.org/wiki/Code_refactoring
[3] the first workshop on refactoring, https://netfiles.uiuc.edu/dig/RefactoringWorkshop
[4] refactoring tutorial on ruby on rail, http://www.good-tutorials.com/tutorials/ruby-on-rails/refactoring