Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2009/wiki 2 2 SJ

2009-10-15T17:02:33Z

Sheng yi:

'''Refactoring If Statement with Polymorphism.'''

== Design Consideration: Reuse and Change ==

One of the most important consideration of Object-Orientation Software Design is 'Reuse' and 'Change' [2][4]. In terms of reuse, we mean to build the new software with the building block from the old software. The importance of 'change' is from the fact that the software is always changing to keep alive. So that how to effectively make change to the source code is critical for the software design.

=== The Problem of If Statement ===

Under the design consideration we have discussed, the problem of if statement is quite obvious: 1. the conditional relationship in function level prevent us to reuse each of the function separately. We can only reuse the whole application as a unit. 2. when we want to change the functionality of a certain function or add a new function we have to trace to every implementation code. Such change is expensive and violate the OO principle 'code to interface instead of implementation'.

=== Example of If statement ===
<pre>
public class Operator
{
string operation;

public int Execute(int x, int y)
{
switch(operation)
{
case "Add":
return x + y;
case "Subtract":
return x - y;
case "Multiply":
return x * y;
case "Divide":
return x / y;
default:
throw new InvalidOperationException("Unsupported operation");
}
}
}
</pre>

In such example of conditional statement on operator, we see that: if we want to reuse function "add" operator in the other code segment, we have to reuse whole Class operator with the value "Add". And if we want to add a new operation "Power", we need to code in the implementation of Class Operator.

== Idea of Polymorphism ==
Facing the problem of the conditional statement, people[2] come up with refactoring method called 'Polymorphism'. The idea of Polymorphism is to replace the highly functional relationship with the subclass override procedure under abstract class. So subclass is created to encapsulate each function in the conditional statement and the conditional relation is replaced by override a common abstract class. The advantage of such idea is to separate the functionality.

=== Definition of Polymorphism ===
According to [1], Subtype polymorphism, almost universally called just polymorphism in the context of object-oriented programming, is the ability of one type, A, to appear as and be used like another type, B.

The primary usage of polymorphism in industry (object-oriented programming theory) is the ability of objects belonging to different types to respond to method, field, or property calls of the same name, each one according to an appropriate type-specific behavior. The programmer (and the program) does not have to know the exact type of the object in advance, and so the exact behavior is determined at run time.

== Example of Refactoring Conditional Statement with Polymorphism ==
*Before refactoring
<pre>
public class Operator
{
string operation;

public int Execute(int x, int y)
{
switch(operation)
{
case "Add":
return x + y;
case "Subtract":
return x - y;
case "Multiply":
return x * y;
case "Divide":
return x / y;
default:
throw new InvalidOperationException("Unsupported operation");
}
}
}
</pre>

*After refactoring
<pre>
public abstract class Operator
{
public abstract int Execute(int x, int y)
}

public class Add : Operator
{
public override int Execute(int x, int y)
{
return x + y;
}
}
public class Subtract : Operator
{
public override int Execute(int x, int y)
{
return x - y;
}
}
public class Multiply: Operator
{
public override int Execute(int x, int y)
{
return x * y;
}
}
public class Divide: Operator
{
public override int Execute(int x, int y)
{
return x / y;
}
}
</pre>
== References ==

[1] Polymorphism in object-oriented programming, http://en.wikipedia.org/wiki/Polymorphism_in_object-oriented_programming

[2] Rene Santaolaya, Olivia G. Fragoso, Joaquín Pérez, Lorenzo Zambrano, Restructuring Conditional Code Structures Using Object Oriented Design Patterns, Lecture Notes in Computer Science.

[3] Refactoring conditional statement, http://sourcemaking.com/refactoring/replace-conditional-with-polymorphism

[4] Object Orientation Design, http://en.wikipedia.org/wiki/Object-oriented_design

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-16T20:25:00Z

Sheng yi: /* Java Example of Refactoring */

== 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 Common Refactorings===
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
|}

=== Ruby Example of Refactoring ===
Before rename:

def badRenameMethod
puts("Hello World");
end

After rename:

def hello
puts("Hello World");
end

Before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

After encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Java Example of Refactoring ===
Before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

After rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

Before encapsulation:

public class encap_field
{
public String field;
}

After encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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)
|-
|[http://www.activestate.com ActiveState Komodo] || N
|-
| [http://www.netbeans.org NetBeans] || N
|-
| [http://www.ruby-ide.com Arachno Ruby] || N
|-
| [http://freeride.rubyforge.org/wiki/wiki.pl FreeRIDE] || N
|-
| [http://www.mondrian-ide.com/ Mondrian Ruby IDE] || N
|-
| [http://www.sapphiresteel.com Ruby in Steel] || N
|-
| [http://www.jetbrains.com/ruby/index.html RubyMine] || Y
|-
| [http://www.eclipse.org Eclipse] (Aptana) || Y
|}

=== Example of Using Ruby Refactoring Tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:r01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:r02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:r03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:r04.jpg|thumb|upright|alt= rename step 5]]
|}

Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step 4]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step 5]]
|}

=== Example of Using Java Refactoring Tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:j01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:j02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:j03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:j04.jpg|thumb|upright|alt= rename step 5]]
| [[Image:j05.jpg|thumb|upright|alt= rename step 6]]
|}
Here the encapsulation of the field "field" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step 4]]
|}

== Comparison of Ruby and Java Refactoring Tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is a dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is a statically typed language, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples (in section 1.3, 1.4) illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-16T20:24:50Z

Sheng yi: /* Java Example of Refactoring */

== 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 Common Refactorings===
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
|}

=== Ruby Example of Refactoring ===
Before rename:

def badRenameMethod
puts("Hello World");
end

After rename:

def hello
puts("Hello World");
end

Before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

After encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Java Example of Refactoring ===
Before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

After rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

Before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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)
|-
|[http://www.activestate.com ActiveState Komodo] || N
|-
| [http://www.netbeans.org NetBeans] || N
|-
| [http://www.ruby-ide.com Arachno Ruby] || N
|-
| [http://freeride.rubyforge.org/wiki/wiki.pl FreeRIDE] || N
|-
| [http://www.mondrian-ide.com/ Mondrian Ruby IDE] || N
|-
| [http://www.sapphiresteel.com Ruby in Steel] || N
|-
| [http://www.jetbrains.com/ruby/index.html RubyMine] || Y
|-
| [http://www.eclipse.org Eclipse] (Aptana) || Y
|}

=== Example of Using Ruby Refactoring Tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:r01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:r02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:r03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:r04.jpg|thumb|upright|alt= rename step 5]]
|}

Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step 4]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step 5]]
|}

=== Example of Using Java Refactoring Tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:j01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:j02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:j03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:j04.jpg|thumb|upright|alt= rename step 5]]
| [[Image:j05.jpg|thumb|upright|alt= rename step 6]]
|}
Here the encapsulation of the field "field" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step 4]]
|}

== Comparison of Ruby and Java Refactoring Tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is a dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is a statically typed language, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples (in section 1.3, 1.4) illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-16T20:24:40Z

Sheng yi: /* Ruby Example of Refactoring */

== 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 Common Refactorings===
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
|}

=== Ruby Example of Refactoring ===
Before rename:

def badRenameMethod
puts("Hello World");
end

After rename:

def hello
puts("Hello World");
end

Before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

After encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Java Example of Refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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)
|-
|[http://www.activestate.com ActiveState Komodo] || N
|-
| [http://www.netbeans.org NetBeans] || N
|-
| [http://www.ruby-ide.com Arachno Ruby] || N
|-
| [http://freeride.rubyforge.org/wiki/wiki.pl FreeRIDE] || N
|-
| [http://www.mondrian-ide.com/ Mondrian Ruby IDE] || N
|-
| [http://www.sapphiresteel.com Ruby in Steel] || N
|-
| [http://www.jetbrains.com/ruby/index.html RubyMine] || Y
|-
| [http://www.eclipse.org Eclipse] (Aptana) || Y
|}

=== Example of Using Ruby Refactoring Tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:r01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:r02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:r03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:r04.jpg|thumb|upright|alt= rename step 5]]
|}

Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step 4]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step 5]]
|}

=== Example of Using Java Refactoring Tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:j01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:j02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:j03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:j04.jpg|thumb|upright|alt= rename step 5]]
| [[Image:j05.jpg|thumb|upright|alt= rename step 6]]
|}
Here the encapsulation of the field "field" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step 4]]
|}

== Comparison of Ruby and Java Refactoring Tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is a dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is a statically typed language, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples (in section 1.3, 1.4) illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-16T20:22:33Z

Sheng yi: /* Refactoring support for Current Ruby IDE */

== 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 Common Refactorings===
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
|}

=== Ruby Example of Refactoring ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
puts("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Java Example of Refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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)
|-
|[http://www.activestate.com ActiveState Komodo] || N
|-
| [http://www.netbeans.org NetBeans] || N
|-
| [http://www.ruby-ide.com Arachno Ruby] || N
|-
| [http://freeride.rubyforge.org/wiki/wiki.pl FreeRIDE] || N
|-
| [http://www.mondrian-ide.com/ Mondrian Ruby IDE] || N
|-
| [http://www.sapphiresteel.com Ruby in Steel] || N
|-
| [http://www.jetbrains.com/ruby/index.html RubyMine] || Y
|-
| [http://www.eclipse.org Eclipse] (Aptana) || Y
|}

=== Example of Using Ruby Refactoring Tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:r01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:r02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:r03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:r04.jpg|thumb|upright|alt= rename step 5]]
|}

Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step 4]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step 5]]
|}

=== Example of Using Java Refactoring Tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:j01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:j02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:j03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:j04.jpg|thumb|upright|alt= rename step 5]]
| [[Image:j05.jpg|thumb|upright|alt= rename step 6]]
|}
Here the encapsulation of the field "field" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step 4]]
|}

== Comparison of Ruby and Java Refactoring Tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is a dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is a statically typed language, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples (in section 1.3, 1.4) illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-16T20:21:52Z

Sheng yi:

== 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 Common Refactorings===
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
|}

=== Ruby Example of Refactoring ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
puts("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Java Example of Refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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)
|-
|[http://www.activestate.com ActiveState Komodo] || N
|-
| [http://www.netbeans.org NetBeans] || N
|-
| [www.ruby-ide.com Arachno Ruby] || N
|-
| [http://freeride.rubyforge.org/wiki/wiki.pl FreeRIDE] || N
|-
| [http://www.mondrian-ide.com/ Mondrian Ruby IDE] || N
|-
| [www.sapphiresteel.com Ruby in Steel] || N
|-
| [www.jetbrains.com/ruby/index.html RubyMine] || Y
|-
| [www.eclipse.org Eclipse] (Aptana) || Y
|}

=== Example of Using Ruby Refactoring Tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:r01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:r02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:r03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:r04.jpg|thumb|upright|alt= rename step 5]]
|}

Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step 4]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step 5]]
|}

=== Example of Using Java Refactoring Tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:j01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:j02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:j03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:j04.jpg|thumb|upright|alt= rename step 5]]
| [[Image:j05.jpg|thumb|upright|alt= rename step 6]]
|}
Here the encapsulation of the field "field" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step 4]]
|}

== Comparison of Ruby and Java Refactoring Tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is a dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is a statically typed language, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples (in section 1.3, 1.4) illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a 9b SJ

2009-09-11T20:16:22Z

Sheng yi: /* Motivation of Refactoring */

== 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 Common Refactorings ===

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
|}

=== Ruby Example of Refactoring ===

before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
puts("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Java Example of Refactoring ===

before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:r01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:r02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:r03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:r04.jpg|thumb|upright|alt= rename step 5]]
|}

Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step 4]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step 5]]
|}

=== Example of Using Java Refactoring Tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:j01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:j02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:j03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:j04.jpg|thumb|upright|alt= rename step 5]]
| [[Image:j05.jpg|thumb|upright|alt= rename step 6]]
|}
Here the encapsulation of the field "field" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step 4]]
|}

== Comparison of Ruby and Java Refactoring Tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages.
Ruby is a dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is a statically typed language,
polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples (in section 1.3, 1.4)
illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a 9b SJ

2009-09-11T20:15:31Z

Sheng yi:

== 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 Common Refactorings ===

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
|}

=== Ruby Example of Refactoring ===

before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
puts("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Java Example of Refactoring ===

before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:r01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:r02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:r03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:r04.jpg|thumb|upright|alt= rename step 5]]
|}

Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step 4]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step 5]]
|}

=== Example of Using Java Refactoring Tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:j01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:j02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:j03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:j04.jpg|thumb|upright|alt= rename step 5]]
| [[Image:j05.jpg|thumb|upright|alt= rename step 6]]
|}
Here the encapsulation of the field "field" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step 4]]
|}

== Comparison of Ruby and Java Refactoring Tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages.
Ruby is a dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is a statically typed language,
polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples (in section 1.3, 1.4)
illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a 9b SJ

2009-09-11T20:09:43Z

Sheng yi:

== 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 Common Refactorings ===

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
|}

=== Ruby Example of Refactoring ===

before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
puts("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Java Example of Refactoring ===

before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:r01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:r02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:r03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:r04.jpg|thumb|upright|alt= rename step 5]]
|}

Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step 4]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step 5]]
|}

=== Example of Using Java Refactoring Tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:j01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:j02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:j03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:j04.jpg|thumb|upright|alt= rename step 5]]
| [[Image:j05.jpg|thumb|upright|alt= rename step 6]]
|}
Here the encapsulation of the field "field" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step 4]]
|}

== Comparison of Ruby and Java Refactoring Tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is a dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is a statically typed language, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples (in section 1.3, 1.4) illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a 9b SJ

2009-09-08T16:39:02Z

Sheng yi:

== 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 Common Refactorings===
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
|}

=== Ruby Example of Refactoring ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
puts("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Java Example of Refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:r01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:r02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:r03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:r04.jpg|thumb|upright|alt= rename step 5]]
|}

Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step 4]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step 5]]
|}

=== Example of Using Java Refactoring Tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:j01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:j02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:j03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:j04.jpg|thumb|upright|alt= rename step 5]]
| [[Image:j05.jpg|thumb|upright|alt= rename step 6]]
|}
Here the encapsulation of the field "field" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step 4]]
|}

== Comparison of Ruby and Java Refactoring Tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is a dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is a statically typed language, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples (in section 1.3, 1.4) illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T04:03:36Z

Sheng yi: /* Comparison of Ruby and Java Refactoring Tools */

== 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 Common Refactorings===
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
|}

=== Ruby Example of Refactoring ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
puts("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Java Example of Refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:r01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:r02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:r03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:r04.jpg|thumb|upright|alt= rename step 5]]
|}

Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step 4]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step 5]]
|}

=== Example of Using Java Refactoring Tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:j01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:j02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:j03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:j04.jpg|thumb|upright|alt= rename step 5]]
| [[Image:j05.jpg|thumb|upright|alt= rename step 6]]
|}
Here the encapsulation of the field "field" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step 4]]
|}

== Comparison of Ruby and Java Refactoring Tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is a dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is a statically typed language, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples (in section 1.3, 1.4) illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T04:02:58Z

Sheng yi: /* Comparison of Ruby and Java Refactoring Tools */

== 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 Common Refactorings===
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
|}

=== Ruby Example of Refactoring ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
puts("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Java Example of Refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:r01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:r02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:r03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:r04.jpg|thumb|upright|alt= rename step 5]]
|}

Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step 4]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step 5]]
|}

=== Example of Using Java Refactoring Tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:j01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:j02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:j03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:j04.jpg|thumb|upright|alt= rename step 5]]
| [[Image:j05.jpg|thumb|upright|alt= rename step 6]]
|}
Here the encapsulation of the field "field" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step 4]]
|}

== Comparison of Ruby and Java Refactoring Tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is a dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is a statically typed language, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T03:58:07Z

Sheng yi: /* Example of Using Java Refactoring Tools in Eclipse */

== 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 Common Refactorings===
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
|}

=== Ruby Example of Refactoring ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
puts("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Java Example of Refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:r01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:r02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:r03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:r04.jpg|thumb|upright|alt= rename step 5]]
|}

Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step 4]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step 5]]
|}

=== Example of Using Java Refactoring Tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:j01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:j02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:j03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:j04.jpg|thumb|upright|alt= rename step 5]]
| [[Image:j05.jpg|thumb|upright|alt= rename step 6]]
|}
Here the encapsulation of the field "field" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step 4]]
|}

== Comparison of Ruby and Java Refactoring Tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is statically typed, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T03:57:11Z

Sheng yi: /* Comparison of Ruby and Java refactoring tools */

== 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 Common Refactorings===
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
|}

=== Ruby Example of Refactoring ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
puts("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Java Example of Refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:r01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:r02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:r03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:r04.jpg|thumb|upright|alt= rename step 5]]
|}

Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step 4]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step 5]]
|}

=== Example of Using Java Refactoring Tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:j01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:j02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:j03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:j04.jpg|thumb|upright|alt= rename step 5]]
| [[Image:j05.jpg|thumb|upright|alt= rename step 6]]
|}
Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.

{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step 4]]
|}

== Comparison of Ruby and Java Refactoring Tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is statically typed, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T03:56:52Z

Sheng yi: /* Example of using Java refactoring tools in Eclipse */

== 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 Common Refactorings===
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
|}

=== Ruby Example of Refactoring ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
puts("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Java Example of Refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:r01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:r02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:r03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:r04.jpg|thumb|upright|alt= rename step 5]]
|}

Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step 4]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step 5]]
|}

=== Example of Using Java Refactoring Tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:j01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:j02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:j03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:j04.jpg|thumb|upright|alt= rename step 5]]
| [[Image:j05.jpg|thumb|upright|alt= rename step 6]]
|}
Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.

{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step 4]]
|}

== Comparison of Ruby and Java refactoring tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is statically typed, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T03:56:37Z

Sheng yi: /* Example of using Ruby refactoring tools in Eclipse */

== 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 Common Refactorings===
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
|}

=== Ruby Example of Refactoring ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
puts("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Java Example of Refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:r01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:r02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:r03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:r04.jpg|thumb|upright|alt= rename step 5]]
|}

Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step 4]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step 5]]
|}

=== Example of using Java refactoring tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:j01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:j02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:j03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:j04.jpg|thumb|upright|alt= rename step 5]]
| [[Image:j05.jpg|thumb|upright|alt= rename step 6]]
|}
Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.

{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step 4]]
|}

== Comparison of Ruby and Java refactoring tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is statically typed, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T03:55:45Z

Sheng yi: /* What is code refactoring */

== 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 Common Refactorings===
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
|}

=== Ruby Example of Refactoring ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
puts("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Java Example of Refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:r01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:r02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:r03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:r04.jpg|thumb|upright|alt= rename step 5]]
|}

Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step 4]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step 5]]
|}

=== Example of using Java refactoring tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:j01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:j02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:j03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:j04.jpg|thumb|upright|alt= rename step 5]]
| [[Image:j05.jpg|thumb|upright|alt= rename step 6]]
|}
Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.

{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step 4]]
|}

== Comparison of Ruby and Java refactoring tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is statically typed, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T03:54:42Z

Sheng yi: /* Example of using Java refactoring tools in Eclipse */

== 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
|}

=== Ruby Example of Refactoring ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
puts("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Java Example of Refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:r01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:r02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:r03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:r04.jpg|thumb|upright|alt= rename step 5]]
|}

Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step 4]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step 5]]
|}

=== Example of using Java refactoring tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:j01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:j02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:j03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:j04.jpg|thumb|upright|alt= rename step 5]]
| [[Image:j05.jpg|thumb|upright|alt= rename step 6]]
|}
Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.

{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step 4]]
|}

== Comparison of Ruby and Java refactoring tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is statically typed, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T03:54:16Z

Sheng yi: /* Example of using Ruby refactoring tools in Eclipse */

== 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
|}

=== Ruby Example of Refactoring ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
puts("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Java Example of Refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step 1]]
| [[Image:r01.jpg|thumb|upright|alt= rename step 2]]
| [[Image:r02.jpg|thumb|upright|alt= rename step 3]]
| [[Image:r03.jpg|thumb|upright|alt= rename step 4]]
| [[Image:r04.jpg|thumb|upright|alt= rename step 5]]
|}

Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step 1]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step 2]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step 3]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step 4]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step 5]]
|}

=== Example of using Java refactoring tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step1]]
| [[Image:j01.jpg|thumb|upright|alt= rename step2]]
| [[Image:j02.jpg|thumb|upright|alt= rename step3]]
| [[Image:j03.jpg|thumb|upright|alt= rename step4]]
| [[Image:j04.jpg|thumb|upright|alt= rename step5]]
| [[Image:j05.jpg|thumb|upright|alt= rename step6]]
|}
Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.

{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step4]]
|}

== Comparison of Ruby and Java refactoring tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is statically typed, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T03:53:22Z

Sheng yi: /* Example of using Java refactoring tools in Eclipse */

== 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
|}

=== Ruby Example of Refactoring ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
puts("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Java Example of Refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step0]]
| [[Image:r01.jpg|thumb|upright|alt= rename step1]]
| [[Image:r02.jpg|thumb|upright|alt= rename step2]]
| [[Image:r03.jpg|thumb|upright|alt= rename step3]]
| [[Image:r04.jpg|thumb|upright|alt= rename step4]]
|}

Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step0]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step4]]
|}

=== Example of using Java refactoring tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step1]]
| [[Image:j01.jpg|thumb|upright|alt= rename step2]]
| [[Image:j02.jpg|thumb|upright|alt= rename step3]]
| [[Image:j03.jpg|thumb|upright|alt= rename step4]]
| [[Image:j04.jpg|thumb|upright|alt= rename step5]]
| [[Image:j05.jpg|thumb|upright|alt= rename step6]]
|}
Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.

{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step4]]
|}

== Comparison of Ruby and Java refactoring tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is statically typed, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T03:52:58Z

Sheng yi: /* Example of using Java refactoring tools in Eclipse */

== 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
|}

=== Ruby Example of Refactoring ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
puts("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Java Example of Refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step0]]
| [[Image:r01.jpg|thumb|upright|alt= rename step1]]
| [[Image:r02.jpg|thumb|upright|alt= rename step2]]
| [[Image:r03.jpg|thumb|upright|alt= rename step3]]
| [[Image:r04.jpg|thumb|upright|alt= rename step4]]
|}

Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step0]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step4]]
|}

=== Example of using Java refactoring tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step0]]
| [[Image:j01.jpg|thumb|upright|alt= rename step1]]
| [[Image:j02.jpg|thumb|upright|alt= rename step2]]
| [[Image:j03.jpg|thumb|upright|alt= rename step3]]
| [[Image:j04.jpg|thumb|upright|alt= rename step4]]
| [[Image:j05.jpg|thumb|upright|alt= rename step0]]
|}
Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.

{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step4]]
|}

== Comparison of Ruby and Java refactoring tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is statically typed, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T03:52:18Z

Sheng yi: /* Example of using Java refactoring tools in Eclipse */

== 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
|}

=== Ruby Example of Refactoring ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
puts("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Java Example of Refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step0]]
| [[Image:r01.jpg|thumb|upright|alt= rename step1]]
| [[Image:r02.jpg|thumb|upright|alt= rename step2]]
| [[Image:r03.jpg|thumb|upright|alt= rename step3]]
| [[Image:r04.jpg|thumb|upright|alt= rename step4]]
|}

Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step0]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step4]]
|}

=== Example of using Java refactoring tools in Eclipse ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Java. The source code is show in section 1.4.

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step0]]
| [[Image:j01.jpg|thumb|upright|alt= rename step1]]
| [[Image:j02.jpg|thumb|upright|alt= rename step2]]
| [[Image:j03.jpg|thumb|upright|alt= rename step3]]
| [[Image:j04.jpg|thumb|upright|alt= rename step4]]
| [[Image:j05.jpg|thumb|upright|alt= rename step0]]
|}

{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step4]]
|}

== Comparison of Ruby and Java refactoring tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is statically typed, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T03:50:47Z

Sheng yi: /* Example of using Ruby refactoring tools in Eclipse */

== 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
|}

=== Ruby Example of Refactoring ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
puts("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Java Example of Refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step0]]
| [[Image:r01.jpg|thumb|upright|alt= rename step1]]
| [[Image:r02.jpg|thumb|upright|alt= rename step2]]
| [[Image:r03.jpg|thumb|upright|alt= rename step3]]
| [[Image:r04.jpg|thumb|upright|alt= rename step4]]
|}

Here the encapsulation of the field "field" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step0]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step4]]
|}

=== Example of using Java refactoring tools in Eclipse ===
example of rename:

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step0]]
| [[Image:j01.jpg|thumb|upright|alt= rename step1]]
| [[Image:j02.jpg|thumb|upright|alt= rename step2]]
| [[Image:j03.jpg|thumb|upright|alt= rename step3]]
| [[Image:j04.jpg|thumb|upright|alt= rename step4]]
| [[Image:j05.jpg|thumb|upright|alt= rename step0]]
|}

example of encapsulation:
{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step4]]
|}

== Comparison of Ruby and Java refactoring tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is statically typed, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T03:49:28Z

Sheng yi: /* Example of using Ruby refactoring tools in Eclipse */

== 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
|}

=== Ruby Example of Refactoring ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
puts("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Java Example of Refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby. The source code is show in section 1.3.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step0]]
| [[Image:r01.jpg|thumb|upright|alt= rename step1]]
| [[Image:r02.jpg|thumb|upright|alt= rename step2]]
| [[Image:r03.jpg|thumb|upright|alt= rename step3]]
| [[Image:r04.jpg|thumb|upright|alt= rename step4]]
|}

Here the renaming of the method "badRenameMethod to "Hello" is illustrated for Java. The source code is show in section 1.4.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step0]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step4]]
|}

=== Example of using Java refactoring tools in Eclipse ===
example of rename:

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step0]]
| [[Image:j01.jpg|thumb|upright|alt= rename step1]]
| [[Image:j02.jpg|thumb|upright|alt= rename step2]]
| [[Image:j03.jpg|thumb|upright|alt= rename step3]]
| [[Image:j04.jpg|thumb|upright|alt= rename step4]]
| [[Image:j05.jpg|thumb|upright|alt= rename step0]]
|}

example of encapsulation:
{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step4]]
|}

== Comparison of Ruby and Java refactoring tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is statically typed, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T03:47:52Z

Sheng yi: /* Ruby Example of refactoring */

== 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
|}

=== Ruby Example of Refactoring ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
puts("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Java Example of Refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step0]]
| [[Image:r01.jpg|thumb|upright|alt= rename step1]]
| [[Image:r02.jpg|thumb|upright|alt= rename step2]]
| [[Image:r03.jpg|thumb|upright|alt= rename step3]]
| [[Image:r04.jpg|thumb|upright|alt= rename step4]]
|}

Here the renaming of the method "badRenameMethod to "Hello" is illustrated for Java.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step0]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step4]]
|}

=== Example of using Java refactoring tools in Eclipse ===
example of rename:

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step0]]
| [[Image:j01.jpg|thumb|upright|alt= rename step1]]
| [[Image:j02.jpg|thumb|upright|alt= rename step2]]
| [[Image:j03.jpg|thumb|upright|alt= rename step3]]
| [[Image:j04.jpg|thumb|upright|alt= rename step4]]
| [[Image:j05.jpg|thumb|upright|alt= rename step0]]
|}

example of encapsulation:
{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step4]]
|}

== Comparison of Ruby and Java refactoring tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is statically typed, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T03:47:41Z

Sheng yi: /* Some Java Example of refactoring */

== 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
|}

=== Ruby Example of refactoring ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
puts("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Java Example of Refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step0]]
| [[Image:r01.jpg|thumb|upright|alt= rename step1]]
| [[Image:r02.jpg|thumb|upright|alt= rename step2]]
| [[Image:r03.jpg|thumb|upright|alt= rename step3]]
| [[Image:r04.jpg|thumb|upright|alt= rename step4]]
|}

Here the renaming of the method "badRenameMethod to "Hello" is illustrated for Java.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step0]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step4]]
|}

=== Example of using Java refactoring tools in Eclipse ===
example of rename:

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step0]]
| [[Image:j01.jpg|thumb|upright|alt= rename step1]]
| [[Image:j02.jpg|thumb|upright|alt= rename step2]]
| [[Image:j03.jpg|thumb|upright|alt= rename step3]]
| [[Image:j04.jpg|thumb|upright|alt= rename step4]]
| [[Image:j05.jpg|thumb|upright|alt= rename step0]]
|}

example of encapsulation:
{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step4]]
|}

== Comparison of Ruby and Java refactoring tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is statically typed, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T03:47:24Z

Sheng yi: /* Some Ruby Example of refactoring */

== 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
|}

=== Ruby Example of refactoring ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
puts("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Some Java Example of refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step0]]
| [[Image:r01.jpg|thumb|upright|alt= rename step1]]
| [[Image:r02.jpg|thumb|upright|alt= rename step2]]
| [[Image:r03.jpg|thumb|upright|alt= rename step3]]
| [[Image:r04.jpg|thumb|upright|alt= rename step4]]
|}

Here the renaming of the method "badRenameMethod to "Hello" is illustrated for Java.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step0]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step4]]
|}

=== Example of using Java refactoring tools in Eclipse ===
example of rename:

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step0]]
| [[Image:j01.jpg|thumb|upright|alt= rename step1]]
| [[Image:j02.jpg|thumb|upright|alt= rename step2]]
| [[Image:j03.jpg|thumb|upright|alt= rename step3]]
| [[Image:j04.jpg|thumb|upright|alt= rename step4]]
| [[Image:j05.jpg|thumb|upright|alt= rename step0]]
|}

example of encapsulation:
{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step4]]
|}

== Comparison of Ruby and Java refactoring tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is statically typed, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T03:46:56Z

Sheng yi: /* Some Ruby Example of refactoring */

== 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 ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
puts("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Some Java Example of refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step0]]
| [[Image:r01.jpg|thumb|upright|alt= rename step1]]
| [[Image:r02.jpg|thumb|upright|alt= rename step2]]
| [[Image:r03.jpg|thumb|upright|alt= rename step3]]
| [[Image:r04.jpg|thumb|upright|alt= rename step4]]
|}

Here the renaming of the method "badRenameMethod to "Hello" is illustrated for Java.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step0]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step4]]
|}

=== Example of using Java refactoring tools in Eclipse ===
example of rename:

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step0]]
| [[Image:j01.jpg|thumb|upright|alt= rename step1]]
| [[Image:j02.jpg|thumb|upright|alt= rename step2]]
| [[Image:j03.jpg|thumb|upright|alt= rename step3]]
| [[Image:j04.jpg|thumb|upright|alt= rename step4]]
| [[Image:j05.jpg|thumb|upright|alt= rename step0]]
|}

example of encapsulation:
{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step4]]
|}

== Comparison of Ruby and Java refactoring tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is statically typed, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T03:46:45Z

Sheng yi: /* Some Ruby Example of refactoring */

== 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 ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
put("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Some Java Example of refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step0]]
| [[Image:r01.jpg|thumb|upright|alt= rename step1]]
| [[Image:r02.jpg|thumb|upright|alt= rename step2]]
| [[Image:r03.jpg|thumb|upright|alt= rename step3]]
| [[Image:r04.jpg|thumb|upright|alt= rename step4]]
|}

Here the renaming of the method "badRenameMethod to "Hello" is illustrated for Java.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step0]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step4]]
|}

=== Example of using Java refactoring tools in Eclipse ===
example of rename:

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step0]]
| [[Image:j01.jpg|thumb|upright|alt= rename step1]]
| [[Image:j02.jpg|thumb|upright|alt= rename step2]]
| [[Image:j03.jpg|thumb|upright|alt= rename step3]]
| [[Image:j04.jpg|thumb|upright|alt= rename step4]]
| [[Image:j05.jpg|thumb|upright|alt= rename step0]]
|}

example of encapsulation:
{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step4]]
|}

== Comparison of Ruby and Java refactoring tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is statically typed, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T03:46:06Z

Sheng yi: /* Example of using Ruby refactoring tools in Eclipse */

== 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 ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
put("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Some Java Example of refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
Here the renaming of the method "badRenameMethod" to "Hello" is illustrated for Ruby.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step0]]
| [[Image:r01.jpg|thumb|upright|alt= rename step1]]
| [[Image:r02.jpg|thumb|upright|alt= rename step2]]
| [[Image:r03.jpg|thumb|upright|alt= rename step3]]
| [[Image:r04.jpg|thumb|upright|alt= rename step4]]
|}

Here the renaming of the method "badRenameMethod to "Hello" is illustrated for Java.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step0]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step4]]
|}

=== Example of using Java refactoring tools in Eclipse ===
example of rename:

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step0]]
| [[Image:j01.jpg|thumb|upright|alt= rename step1]]
| [[Image:j02.jpg|thumb|upright|alt= rename step2]]
| [[Image:j03.jpg|thumb|upright|alt= rename step3]]
| [[Image:j04.jpg|thumb|upright|alt= rename step4]]
| [[Image:j05.jpg|thumb|upright|alt= rename step0]]
|}

example of encapsulation:
{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step4]]
|}

== Comparison of Ruby and Java refactoring tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is statically typed, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T03:44:54Z

Sheng yi: /* Example of using Ruby refactoring tools in Eclipse */

== 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 ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
put("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Some Java Example of refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
example of rename:
Here the renaming of the method badRameMethod to Hello is illustrated for Ruby.
{|
| [[Image:r00.jpg|thumb|upright|alt= rename step0]]
| [[Image:r01.jpg|thumb|upright|alt= rename step1]]
| [[Image:r02.jpg|thumb|upright|alt= rename step2]]
| [[Image:r03.jpg|thumb|upright|alt= rename step3]]
| [[Image:r04.jpg|thumb|upright|alt= rename step4]]
|}

example of encapsulation:
Here the renaming of the method badRameMethod to Hello is illustrated for Java.
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step0]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step4]]
|}

=== Example of using Java refactoring tools in Eclipse ===
example of rename:

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step0]]
| [[Image:j01.jpg|thumb|upright|alt= rename step1]]
| [[Image:j02.jpg|thumb|upright|alt= rename step2]]
| [[Image:j03.jpg|thumb|upright|alt= rename step3]]
| [[Image:j04.jpg|thumb|upright|alt= rename step4]]
| [[Image:j05.jpg|thumb|upright|alt= rename step0]]
|}

example of encapsulation:
{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step4]]
|}

== Comparison of Ruby and Java refactoring tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is statically typed, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T03:41:25Z

Sheng yi: /* Comparison of Ruby and Java refactoring tools */

== 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 ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
put("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Some Java Example of refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
example of rename:

{|
| [[Image:r00.jpg|thumb|upright|alt= rename step0]]
| [[Image:r01.jpg|thumb|upright|alt= rename step1]]
| [[Image:r02.jpg|thumb|upright|alt= rename step2]]
| [[Image:r03.jpg|thumb|upright|alt= rename step3]]
| [[Image:r04.jpg|thumb|upright|alt= rename step4]]
|}

example of encapsulation:
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step0]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step4]]
|}

=== Example of using Java refactoring tools in Eclipse ===
example of rename:

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step0]]
| [[Image:j01.jpg|thumb|upright|alt= rename step1]]
| [[Image:j02.jpg|thumb|upright|alt= rename step2]]
| [[Image:j03.jpg|thumb|upright|alt= rename step3]]
| [[Image:j04.jpg|thumb|upright|alt= rename step4]]
| [[Image:j05.jpg|thumb|upright|alt= rename step0]]
|}

example of encapsulation:
{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step4]]
|}

== Comparison of Ruby and Java refactoring tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse |||| 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is statically typed, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T03:41:03Z

Sheng yi: /* Comparison of Ruby and Java refactoring tools */

== 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 ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
put("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Some Java Example of refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
example of rename:

{|
| [[Image:r00.jpg|thumb|upright|alt= rename step0]]
| [[Image:r01.jpg|thumb|upright|alt= rename step1]]
| [[Image:r02.jpg|thumb|upright|alt= rename step2]]
| [[Image:r03.jpg|thumb|upright|alt= rename step3]]
| [[Image:r04.jpg|thumb|upright|alt= rename step4]]
|}

example of encapsulation:
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step0]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step4]]
|}

=== Example of using Java refactoring tools in Eclipse ===
example of rename:

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step0]]
| [[Image:j01.jpg|thumb|upright|alt= rename step1]]
| [[Image:j02.jpg|thumb|upright|alt= rename step2]]
| [[Image:j03.jpg|thumb|upright|alt= rename step3]]
| [[Image:j04.jpg|thumb|upright|alt= rename step4]]
| [[Image:j05.jpg|thumb|upright|alt= rename step0]]
|}

example of encapsulation:
{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step4]]
|}

== Comparison of Ruby and Java refactoring tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse || || 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || || Rename
|-
|Move || || Move
|-
|Change Method Signature || || Merge Class Parts in File
|-
|Extract Local Variable || || Pull Up
|-
|Extract Constant || || Pull Down
|-
|Inline || || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || || Split Local Variable
|-
|Convert Member to Top Level || || Merge With External Class Parts
|-
|Convert Local Variable to Field || || Inline
|-
|Extract Super Class || || Extract Constant
|-
|Extract Interface || || Encapsulate Field
|-
|Extract Class || || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is statically typed, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T03:40:24Z

Sheng yi: /* Comparison of Ruby and Java refactoring tools */

== 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 ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
put("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Some Java Example of refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
example of rename:

{|
| [[Image:r00.jpg|thumb|upright|alt= rename step0]]
| [[Image:r01.jpg|thumb|upright|alt= rename step1]]
| [[Image:r02.jpg|thumb|upright|alt= rename step2]]
| [[Image:r03.jpg|thumb|upright|alt= rename step3]]
| [[Image:r04.jpg|thumb|upright|alt= rename step4]]
|}

example of encapsulation:
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step0]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step4]]
|}

=== Example of using Java refactoring tools in Eclipse ===
example of rename:

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step0]]
| [[Image:j01.jpg|thumb|upright|alt= rename step1]]
| [[Image:j02.jpg|thumb|upright|alt= rename step2]]
| [[Image:j03.jpg|thumb|upright|alt= rename step3]]
| [[Image:j04.jpg|thumb|upright|alt= rename step4]]
| [[Image:j05.jpg|thumb|upright|alt= rename step0]]
|}

example of encapsulation:
{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step4]]
|}

== Comparison of Ruby and Java refactoring tools ==
Comprehensiveness comparison:

{|
|1. Refactoring Options for Java in Eclipse || || 2. Refactoring Options in Eclipse for Ruby
|-
|Rename || Rename
|-
|Move || Move
|-
|Change Method Signature || Merge Class Parts in File
|-
|Extract Local Variable || Pull Up
|-
|Extract Constant || Pull Down
|-
|Inline || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || Split Local Variable
|-
|Convert Member to Top Level || Merge With External Class Parts
|-
|Convert Local Variable to Field || Inline
|-
|Extract Super Class || Extract Constant
|-
|Extract Interface || Encapsulate Field
|-
|Extract Class || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is statically typed, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T03:39:10Z

Sheng yi:

== 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 ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
put("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Some Java Example of refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
example of rename:

{|
| [[Image:r00.jpg|thumb|upright|alt= rename step0]]
| [[Image:r01.jpg|thumb|upright|alt= rename step1]]
| [[Image:r02.jpg|thumb|upright|alt= rename step2]]
| [[Image:r03.jpg|thumb|upright|alt= rename step3]]
| [[Image:r04.jpg|thumb|upright|alt= rename step4]]
|}

example of encapsulation:
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step0]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step4]]
|}

=== Example of using Java refactoring tools in Eclipse ===
example of rename:

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step0]]
| [[Image:j01.jpg|thumb|upright|alt= rename step1]]
| [[Image:j02.jpg|thumb|upright|alt= rename step2]]
| [[Image:j03.jpg|thumb|upright|alt= rename step3]]
| [[Image:j04.jpg|thumb|upright|alt= rename step4]]
| [[Image:j05.jpg|thumb|upright|alt= rename step0]]
|}

example of encapsulation:
{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step4]]
|}

== Comparison of Ruby and Java refactoring tools ==
Comprehensiveness comparison:

{|
|Refactoring Options for Java in Eclipse || Refactoring Options in Eclipse for Ruby
|-
|Rename || Rename
|-
|Move || Move
|-
|Change Method Signature || Merge Class Parts in File
|-
|Extract Local Variable || Pull Up
|-
|Extract Constant || Pull Down
|-
|Inline || Merge With External Class Parts
|-
|Convert Anonymous Class to Nested || Split Local Variable
|-
|Convert Member to Top Level || Merge With External Class Parts
|-
|Convert Local Variable to Field || Inline
|-
|Extract Super Class || Extract Constant
|-
|Extract Interface || Encapsulate Field
|-
|Extract Class || Convert Local Variable to Field
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is statically typed, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T03:31:06Z

Sheng yi: /* Ruby vs Java in terms of refactoring */

== 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 ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
put("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Some Java Example of refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
example of rename:

{|
| [[Image:r00.jpg|thumb|upright|alt= rename step0]]
| [[Image:r01.jpg|thumb|upright|alt= rename step1]]
| [[Image:r02.jpg|thumb|upright|alt= rename step2]]
| [[Image:r03.jpg|thumb|upright|alt= rename step3]]
| [[Image:r04.jpg|thumb|upright|alt= rename step4]]
|}

example of encapsulation:
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step0]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step4]]
|}

=== Example of using Java refactoring tools in Eclipse ===
example of rename:

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step0]]
| [[Image:j01.jpg|thumb|upright|alt= rename step1]]
| [[Image:j02.jpg|thumb|upright|alt= rename step2]]
| [[Image:j03.jpg|thumb|upright|alt= rename step3]]
| [[Image:j04.jpg|thumb|upright|alt= rename step4]]
| [[Image:j05.jpg|thumb|upright|alt= rename step0]]
|}

example of encapsulation:
{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step4]]
|}

== Comparison of Ruby and Java refactoring tools ==
Comprehensiveness:
{|Refactoring Options for Ruby in Eclipse
|-
|Convert Local Variable to Field
|-
|Encapsulate Field
|-
|Extract Constant
|-
|Inline
|-
|Merge Class Parts in File
|-
|Merge With External Class Parts
|-
|Move
|-
|Pull Up
|-
|Pull Down
|-
|Rename
|-
|Split Local Variable
|}

{|Refactoring Options in Eclipse for Java
|Rename
|-
|Move
|-
|Change Method Signature
|-
|Extract Local Variable
|-
|Extract Constant
|-
|Inline
|-
|Convert Anonymous Class to Nested
|-
|Convert Member to Top Level
|-
|Convert Local Variable to Field
|-
|Extract Super Class
|-
|Extract Interface
|-
|Extract Class
|-
|Use Supertype where possible
|-
|Pull Up
|-
|Pull Down
|-
|Introduce Parameter Object
|-
|Introduce Indirection
|-
|Introduce Factory
|-
|Introduce Parameter
|-
|Encapsulate Field
|-
|Generalize Declared Type
|-
|Infer Generic Type Arguments
|}

The refactoring options for Ruby and Java cover all the basic refactorings. The differences in the number of options mainly come from the difference in the two languages. Ruby is dynamically typed language, has unbounded polymorphism, and all classes are open to extension. On the other hand, Java is statically typed, polymorphism is mainly implemented via interfaces and inheritance, and classes cannot be extended at runtime. The given examples illustrate the ease of use of the refactoring tools for both Ruby and Java and how well these tools are integrated into the Eclipse IDE.

== 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

CSC/ECE 517 Fall 2009/wiki 1a SJ

2009-09-06T03:25:21Z

Sheng yi:

== 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 ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
put("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Some Java Example of refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
example of rename:

{|
| [[Image:r00.jpg|thumb|upright|alt= rename step0]]
| [[Image:r01.jpg|thumb|upright|alt= rename step1]]
| [[Image:r02.jpg|thumb|upright|alt= rename step2]]
| [[Image:r03.jpg|thumb|upright|alt= rename step3]]
| [[Image:r04.jpg|thumb|upright|alt= rename step4]]
|}

example of encapsulation:
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step0]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step4]]
|}

=== Example of using Java refactoring tools in Eclipse ===
example of rename:

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step0]]
| [[Image:j01.jpg|thumb|upright|alt= rename step1]]
| [[Image:j02.jpg|thumb|upright|alt= rename step2]]
| [[Image:j03.jpg|thumb|upright|alt= rename step3]]
| [[Image:j04.jpg|thumb|upright|alt= rename step4]]
| [[Image:j05.jpg|thumb|upright|alt= rename step0]]
|}

example of encapsulation:
{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step4]]
|}

== 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

CSC/ECE 517 Fall 2009/wiki 1a

2009-09-06T03:21:39Z

Sheng yi:

User:Sheng yi

2009-09-06T03:20:55Z

Sheng yi:

CSC/ECE 517 Fall 2009/wiki 1a/sheng yi

2009-09-06T03:20:35Z

Sheng yi:

== 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 ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
put("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Some Java Example of refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
example of rename:

{|
| [[Image:r00.jpg|thumb|upright|alt= rename step0]]
| [[Image:r01.jpg|thumb|upright|alt= rename step1]]
| [[Image:r02.jpg|thumb|upright|alt= rename step2]]
| [[Image:r03.jpg|thumb|upright|alt= rename step3]]
| [[Image:r04.jpg|thumb|upright|alt= rename step4]]
|}

example of encapsulation:
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step0]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step4]]
|}

=== Example of using Java refactoring tools in Eclipse ===
example of rename:

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step0]]
| [[Image:j01.jpg|thumb|upright|alt= rename step1]]
| [[Image:j02.jpg|thumb|upright|alt= rename step2]]
| [[Image:j03.jpg|thumb|upright|alt= rename step3]]
| [[Image:j04.jpg|thumb|upright|alt= rename step4]]
| [[Image:j05.jpg|thumb|upright|alt= rename step0]]
|}

example of encapsulation:
{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step4]]
|}

== 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

User:Sheng yi

2009-09-06T03:19:19Z

Sheng yi:

== 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 ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
put("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Some Java Example of refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
example of rename:

{|
| [[Image:r00.jpg|thumb|upright|alt= rename step0]]
| [[Image:r01.jpg|thumb|upright|alt= rename step1]]
| [[Image:r02.jpg|thumb|upright|alt= rename step2]]
| [[Image:r03.jpg|thumb|upright|alt= rename step3]]
| [[Image:r04.jpg|thumb|upright|alt= rename step4]]
|}

example of encapsulation:
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step0]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step4]]
|}

=== Example of using Java refactoring tools in Eclipse ===
example of rename:

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step0]]
| [[Image:j01.jpg|thumb|upright|alt= rename step1]]
| [[Image:j02.jpg|thumb|upright|alt= rename step2]]
| [[Image:j03.jpg|thumb|upright|alt= rename step3]]
| [[Image:j04.jpg|thumb|upright|alt= rename step4]]
| [[Image:j05.jpg|thumb|upright|alt= rename step0]]
|}

example of encapsulation:
{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step4]]
|}

== 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

CSC/ECE 517 Fall 2009/wiki 1a

2009-09-06T03:13:09Z

Sheng yi:

== 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 ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
put("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Some Java Example of refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
example of rename:

{|
| [[Image:r00.jpg|thumb|upright|alt= rename step0]]
| [[Image:r01.jpg|thumb|upright|alt= rename step1]]
| [[Image:r02.jpg|thumb|upright|alt= rename step2]]
| [[Image:r03.jpg|thumb|upright|alt= rename step3]]
| [[Image:r04.jpg|thumb|upright|alt= rename step4]]
|}

example of encapsulation:
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step0]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step4]]
|}

=== Example of using Java refactoring tools in Eclipse ===
example of rename:

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step0]]
| [[Image:j01.jpg|thumb|upright|alt= rename step1]]
| [[Image:j02.jpg|thumb|upright|alt= rename step2]]
| [[Image:j03.jpg|thumb|upright|alt= rename step3]]
| [[Image:j04.jpg|thumb|upright|alt= rename step4]]
| [[Image:j05.jpg|thumb|upright|alt= rename step0]]
|}

example of encapsulation:
{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step4]]
|}

== 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

User talk:Sheng yi

2009-09-06T03:02:59Z

Sheng yi: /* Some Java Example of refactoring */

== 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 ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
put("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Some Java Example of refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
private int field;

public void setField(int field)
{
this.field = field;
}

public int getField()
{
return field;
}
}

== 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 ===
example of rename:

{|
| [[Image:r00.jpg|thumb|upright|alt= rename step0]]
| [[Image:r01.jpg|thumb|upright|alt= rename step1]]
| [[Image:r02.jpg|thumb|upright|alt= rename step2]]
| [[Image:r03.jpg|thumb|upright|alt= rename step3]]
| [[Image:r04.jpg|thumb|upright|alt= rename step4]]
|}

example of encapsulation:
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step0]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step4]]
|}

=== Example of using Java refactoring tools in Eclipse ===
example of rename:

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step0]]
| [[Image:j01.jpg|thumb|upright|alt= rename step1]]
| [[Image:j02.jpg|thumb|upright|alt= rename step2]]
| [[Image:j03.jpg|thumb|upright|alt= rename step3]]
| [[Image:j04.jpg|thumb|upright|alt= rename step4]]
| [[Image:j05.jpg|thumb|upright|alt= rename step0]]
|}

example of encapsulation:
{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step4]]
|}

== 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

User talk:Sheng yi

2009-09-06T03:00:33Z

Sheng yi: /* Some Ruby Example of refactoring */

== 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 ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
put("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Some Java Example of refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
public String field;
}

== 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 ===
example of rename:

{|
| [[Image:r00.jpg|thumb|upright|alt= rename step0]]
| [[Image:r01.jpg|thumb|upright|alt= rename step1]]
| [[Image:r02.jpg|thumb|upright|alt= rename step2]]
| [[Image:r03.jpg|thumb|upright|alt= rename step3]]
| [[Image:r04.jpg|thumb|upright|alt= rename step4]]
|}

example of encapsulation:
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step0]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step4]]
|}

=== Example of using Java refactoring tools in Eclipse ===
example of rename:

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step0]]
| [[Image:j01.jpg|thumb|upright|alt= rename step1]]
| [[Image:j02.jpg|thumb|upright|alt= rename step2]]
| [[Image:j03.jpg|thumb|upright|alt= rename step3]]
| [[Image:j04.jpg|thumb|upright|alt= rename step4]]
| [[Image:j05.jpg|thumb|upright|alt= rename step0]]
|}

example of encapsulation:
{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step4]]
|}

== 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

User talk:Sheng yi

2009-09-06T02:59:07Z

Sheng yi: /* Some Java Example of refactoring */

== 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 ===
before rename:

def badRenameMethod
puts("Hello World");
end

after rename:

def hello
("Hello World");
end

before encapsulation:

class SomeClass
def initialize
@field = 0;
end
end

after encapsulation:

class SomeClass
def initialize
@field = 0;
end

def field
@field
end
private :field

def field= field
@field = field
end
private :field=
end

=== Some Java Example of refactoring ===
before rename:

public class rename_method
{
static void badRenameMethod()
{
System.out.println("Hello, world!");
}
}

after rename:

public class rename_method
{
static void hello()
{
System.out.println("Hello, world!");
}
}

before encapsulation:

public class encap_field
{
public String field;
}

after encapsulation:

public class encap_field
{
public String field;
}

== 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 ===
example of rename:

{|
| [[Image:r00.jpg|thumb|upright|alt= rename step0]]
| [[Image:r01.jpg|thumb|upright|alt= rename step1]]
| [[Image:r02.jpg|thumb|upright|alt= rename step2]]
| [[Image:r03.jpg|thumb|upright|alt= rename step3]]
| [[Image:r04.jpg|thumb|upright|alt= rename step4]]
|}

example of encapsulation:
{|
| [[Image:r05.jpg|thumb|upright|alt= encapsulation step0]]
| [[Image:r06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:r07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:r08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:r09.jpg|thumb|upright|alt= encapsulation step4]]
|}

=== Example of using Java refactoring tools in Eclipse ===
example of rename:

{|
| [[Image:j00.jpg|thumb|upright|alt= rename step0]]
| [[Image:j01.jpg|thumb|upright|alt= rename step1]]
| [[Image:j02.jpg|thumb|upright|alt= rename step2]]
| [[Image:j03.jpg|thumb|upright|alt= rename step3]]
| [[Image:j04.jpg|thumb|upright|alt= rename step4]]
| [[Image:j05.jpg|thumb|upright|alt= rename step0]]
|}

example of encapsulation:
{|
| [[Image:j06.jpg|thumb|upright|alt= encapsulation step1]]
| [[Image:j07.jpg|thumb|upright|alt= encapsulation step2]]
| [[Image:j08.jpg|thumb|upright|alt= encapsulation step3]]
| [[Image:j09.jpg|thumb|upright|alt= encapsulation step4]]
|}

== 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

User talk:Sheng yi

2009-09-06T02:56:08Z

Sheng yi: /* Some Ruby Example of refactoring */

User talk:Sheng yi

2009-09-06T02:47:36Z

Sheng yi:

User talk:Sheng yi

2009-09-06T02:36:58Z

Sheng yi:

File:J09.jpg

2009-09-06T02:35:52Z

Sheng yi:

File:J08.jpg

2009-09-06T02:35:39Z

Sheng yi: