CSC/ECE 517 Fall 2014/ch1b 32 sj
Refactoring Browsers in Popular IDEs
What are refactoring browsers?
Have you ever extracted a method by hand? You know, picking out the code you want to extract into a separate method, typing out a method declaration for it, copy-pasting the code, and tweaking the parameters to get everything right? What about renaming a method by hand, or copy-pasting a method or variable from one class to another?
Refactoring browsers greatly simplify the work of many common types of refactoring by providing a graphical interface that programmers can interact with directly to perform these actions. Usually,
Why should refactoring browsers be used?
How to Use Refactoring Browsers
Glossary
- Class browser
- A class browser is a feature of an integrated development environment (IDE) that allows the programmer to browse, navigate, or visualize the structure of object-oriented programming code.
- Refactoring browser
- A refactoring browser allows the programmer to use a graphical interface (usually a class browser) to manipulate, combine, and separate code elements.
Examples of Refactoring Browsers
Grails: http://grails.org/plugin/asset-pipeline
Sample Reference
<ref>"Ruby on Rails 3.1 Release Notes", Rails Guides. Retrieved 17 September 2014.</ref>
References
<references/>