High velocity refactorings in Eclipse
E Murphy-Hill, AP Black - Proceedings of the 2007 OOPSLA workshop …, 2007 - dl.acm.org
Proceedings of the 2007 OOPSLA workshop on eclipse technology eXchange, 2007•dl.acm.org
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 …
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 …
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.
ACM Digital Library