|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ABSTRACT
In Eclipse, and in most other development environments, refactorings are activated by selecting code, then using a menu or hotkey, and finally engaging in a dialog with a "wizard". However, selection is error-prone, menus are slow, hotkeys are hard to remember, and wizards are time-consuming. The problem is that as a consequence, refactoring tools disrupt the programmer's workflow and are perceived to be slower than refactoring by hand. In this paper we present two new user interfaces to Eclipse's existing refactoring engine: marking menus and refactoring cues. Both are designed to increase programming velocity by keeping the tool out of the programmer's way. REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
INDEX TERMS
Primary Classification:
Additional Classification:
General Terms:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||