Reusable Hierarchical Command Objects Export

@inproceedings{Myer96, abstract = {The Amulet user interface development environment uses hierarchical command objects to support the creation of highly-interactive graphical user interfaces. When input arrives or a widget is operated by the user, instead of invoking a call-back procedure as in most other toolkits, Amulet allocates a command object and calls its DO method. Unlike previous uses of command objects, Amulet organizes the commands into a hierarchy, so that low-level operations like dragging or selection invoke low-level commands, which in turn might invoke widget-level commands, which invoke high-level, application-specific commands, and so on. The top-level commands correspond to semantic actions of the program. The result is better modularization because different levels of the user interface are independent, and better code reuse because the lower-level commands, and even many high-level commands such as cut, copy, paste, text edit, and change-color, can be reused from the library. Furthermore, the commands in Amulet support a new form of Undo, where the user can select any previous operation and selectively undo it, repeat it on the same objects, or repeat it on new objects. In addition, operations like scrolling and selections can be undone or repeated, which can be very useful. Thus, the command objects in Amulet make it easier for developers by providing more reusable components, while at the same time providing new capabilities for users.}, address = {Vancouver, BC, Canada}, author = {Myers, Brad A. and Kosbie, David S.}, citeulike-article-id = {382949}, citeulike-linkout-0 = {http://www.cs.cmu.edu/~amulet/papers/commandsCHI.html}, comment = {This is cited for my Slate "Chalk" user interface architecture as a basis for its input event handling design.}, day = {14}, journal = {Proceedings CHI'96: Human Factors in Computing Systems}, keywords = {amulet, command, development, environment, interface, objects, redo, toolkits, undo, user}, month = {April}, organization = {CHI}, posted-at = {2005-11-07 18:00:41}, priority = {0}, school = {Carnegie Mellon University}, title = {Reusable Hierarchical Command Objects}, url = {http://www.cs.cmu.edu/~amulet/papers/commandsCHI.html}, year = {1996} }

TY - CONF ID - Myer96 L3 - citeulike-article-id:382949 N2 - The Amulet user interface development environment uses hierarchical command objects to support the creation of highly-interactive graphical user interfaces. When input arrives or a widget is operated by the user, instead of invoking a call-back procedure as in most other toolkits, Amulet allocates a command object and calls its DO method. Unlike previous uses of command objects, Amulet organizes the commands into a hierarchy, so that low-level operations like dragging or selection invoke low-level commands, which in turn might invoke widget-level commands, which invoke high-level, application-specific commands, and so on. The top-level commands correspond to semantic actions of the program. The result is better modularization because different levels of the user interface are independent, and better code reuse because the lower-level commands, and even many high-level commands such as cut, copy, paste, text edit, and change-color, can be reused from the library. Furthermore, the commands in Amulet support a new form of Undo, where the user can select any previous operation and selectively undo it, repeat it on the same objects, or repeat it on new objects. In addition, operations like scrolling and selections can be undone or repeated, which can be very useful. Thus, the command objects in Amulet make it easier for developers by providing more reusable components, while at the same time providing new capabilities for users. JF - Proceedings CHI'96: Human Factors in Computing Systems OR - CHI AD - Vancouver, BC, Canada TI - Reusable Hierarchical Command Objects KW - amulet KW - command KW - development KW - environment KW - interface KW - objects KW - redo KW - toolkits KW - undo KW - user N1 - This is cited for my Slate "Chalk" user interface architecture as a basis for its input event handling design. AU - Myers, Brad AU - Kosbie, David PY - 1996/04/14/18 UR - http://www.cs.cmu.edu/~amulet/papers/commandsCHI.html ER -