Myers, B.A. and Kosbie, D. "Reusable Hierarchical Command Objects," in CHI 1996. Vancouver, BC, Canada: pp. 260-267.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....strong aprioriexpectations about results. Automated assistance was not a factor in our evaluation, but is a part of the overall design of the system. There has been some interest in decision space navigation, for user interface wizards [2] techniques for non linear undo functionality [7], and decision support environments of all kinds. Our work applies the same ideas to the statistical exploration domain. Experiments with the data mountain interface have been targeted at the organization of bookmarked Web pages [9] The data mountain exploits our spatial cognition abilities to ....

B. A. Myers and D. S. Kosbie. Reusable hierarchical command objects. In Proceedings of CHI '96 (ACM Conference on Human Factors in Computing), pages 260--267. ACM Press, 1996.

....binding was an assumption about the complexity of linking MMTK components to presentation components. Specifically, we assumed that all presentation task communication could be implemented by event synchronization and that the initiation of a communication could be implemented using Amulet Command[71] objects. Clearly things worked out for the examples we tried, but it is reasonable to ask if there exist situations whose complexity exceeds the facilities we have laid down. That is, is our presentation linkage strategy complete with respect to the target toolkit. We believe, in fact, that our ....

....if there exist situations whose complexity exceeds the facilities we have laid down. That is, is our presentation linkage strategy complete with respect to the target toolkit. We believe, in fact, that our approach is complete with respect to the way the Amulet toolkit handles interactor actions[71]. In general there are three obstacles to MMTK presentation linkage: 1. Techniques for connecting UI functionality vary widely depending upon the presentation toolkit and programming language. Connecting with presentation entities often requires setting values in toolkit objects and being ....

[Article contains additional citation context not shown here]

Brad A. Myers and David S. Kosbie. Reusable hierarchical command objects. In CHI'96: Human Factors in Computing Systems, 1996.

....in other ways. Indeed, the same framework has already been used to study the related issue of history mechanisms in hypertext systems and world wide web browsers [9] 1. 2 Undo linear and non linear The issue of undo in user interfaces has been studied by several authors over many years (e.g. [2, 15, 25, 22, 18]) Indeed, the ability to undo (not necessarily with an undo button) is seen as one of the key features of the direct manipulation paradigm [20] However, undo is far from a solved problem. Experiments have shown that even experienced users of word prcessors nd it dif cult to work out what undo ....

B. A. Myers and D. S. Kosbie. Reusable hierarchical command objects. In Proceedings of CHI 96, Vancouver, BC, Canada, pages 260267. ACM Press, 1996.

....of a command with the maintenance of UI state. For example, the procedure that is invoked when a button is pressed might invoke a command and then establish the next state of the UI by enabling some widgets and disabling others. Call back designs often degrade into an unstructured maze of code [16]. Model based synthesis is concerned with generating components from models and tailoring component interfaces so that the right amount of context is exposed. MASTERMIND code generators create components whose interfaces expose any values that were identified as either a source or a target of an ....

B. A. Myers and D. S. Kosbie. Reusable hierarchical command objects. In CHI'96: Human Factors in Computing Systems, 1996.

....that are to be found in interactive systems and helps shed light on the fundamental re exive nature of undo. URL for related work: http: www.soooooooo 1 Introduction and background 1. 1 Undo The issue of undo in user interfaces has been studied by several authors over many years (e.g. [2, 13, 21, 19, 15]) This has included both work aimed at understanding the problem, and workon implementation structures. Despite this, experiments have shown that experienced users of Microsoft Word, which has a relatively simple and easy to use undo function, still have great dif culty in working out what undo ....

B. A. Myers and D. S. Kosbie. Reusable hierarchical command objects. In Proceedings of CHI 96, Vancouver, BC, Canada, pages 260267. ACM Press, 1996.

....internally within the system in order to maintain consistency. These messages are often used to maintain constraints between graphical objects or to notify objects that a graphical object has been deleted. Commands are a common design pattern used for supporting macros, as well as undo and redo [13, 35]. Commands reify operations by encapsulating a transaction into an object that knows how to do, undo, and redo itself. SATIN s command subsystem extends the one provided in Java Swing (javax.swing.undo) by adding in the notion of executing a command (instead of simply undoing an operation) The ....

Myers, B. and D. Kosbie. Reusable Hierarchical Command Objects. In Proceedings of CHI'96. Vancouver, BC, Canada: ACM Press 1006.

....simultaneously in the plot chart. Any applicable database update to the budget object would be reflected in the temporal subabstraction. Updates to the temporal subabstraction are just a shortcut for updating the budget object in Q3, 4 scenario. 12 9. Related Work 9.1. Undo Myers and Kosbie [14] introduce an elegant mechanism for hierarchical undo. Each interface action is given a DO and UNDO method, and a pointer to its parent action, if any. This allows the user to undo an entire semantic action, or just the subactions (e.g. a dialog box action) By adding the context layer to the ....

Myers, B.A. and D.S. Kosbie. Reusable hierarchical command objects. in Human Factors in Computing Systems (SIGCHI). 1996. Vancouver, BC, Canada: ACM Press: p. 260-267.

....Microsoft Word support such features, allowing users to effectively roll back the history of their interaction with the application. More recently, a number of systems in the research literature have explored richer models of application history. These include such tools as GINA [1] and Amulet [13], which use a complex branching model of time for undo and redo operations; Chimera [12] which provides a history model which preserves dependency relationships between operations; WeMet [16] which provides tools for rapidly scanning shared timelines; and Timewarp [4] which uses Published in ....

Myers, B. and Kosbie, D. "Reusable Hierarchical Command Objects," Proc. ACM Conference on Computer-Human Interaction. April, 1996.

....mediation is completed, OOPS stores information about all known possible interpretations. We refer to the input as ambiguous at this point. Information about ambiguity is kept in a hierarchical ambiguous event graph in OOPS (which can be seen as an extension of the command objects described in [24]) Raw input such as mouse down, drag, and up events make up the root nodes of that graph. Whenever input is interpreted, a node representing the new interpretation is added to the graph. For example, the graph shown in Figure 3(b) represents a series of mouse events that have been interpreted as ....

Myers, B.A. and D.S. Kosbie. (1996) Reusable hierarchical command objects. In Proc. of CHI'96, pp. 260--267.

....produces text events, they will be dispatched through the same mechanism as characters produced by a keyboard, and thus will be available to anything that consumes keyboard input. Additionally, OOPS provides an internal model of recognized input, based on the concept of hierarchical events [16], that allows separation of mediation from recognition and from the application. As we will see, this is a key abstraction that we use in the extended Context Toolkit. Our model uses a directed graph to keep track of source events, and their interpretations (which are produced by one or more ....

Myers, B.A. and Kosbie, D.S. Reusable hierarchical command objects. In Proceedings of CHI `96, pp. 260267.

....simultaneously in the plot chart. Any applicable database update to the budget object would be reflected in the temporal subabstraction. Updates to the temporal subabstraction are just a shortcut for updating the budget object in Q3, 4 scenario. 9. Related Work 9.1. Undo Myers and Kosbie [14] introduce an elegant mechanism for hierarchical undo. Each interface action is given a DO and UNDO method, and a pointer to its parent action, if any. This allows the user to undo an entire semantic action, or just the subactions (e.g. a dialog box action) By adding the context layer to the ....

Myers, B.A. and D.S. Kosbie. Reusable hierarchical command objects. in Human Factors in Computing Systems (SIGCHI) . 1996. Vancouver, BC, Canada: ACM Press, p. 260-267.

....all drawing is handled by the system. The executable form for the rules should be straightforward to represent in Amulet. Amulet s object system should be sufficient to use directly as Gamut s object system. Behaviors correspond to interactors [28] and the actions correspond to command objects [29]. Using command objects, a new abstraction specific to Amulet, may also be a simple way to implement Gamut s timeline. Data descriptions do not exist in Amulet so they will have to be designed and implemented. Likewise, the conditional portions of behavior are not well modelled in Amulet ....

Brad A. Myers and David Kosbie. Reusable Hierarchical Command objects. Submitted to CHI'96, 1995.

....potential interpretations into the interface is also difficult without the support of the toolkit. There is a lot of work on introducing undo reversibility into GUI toolkits, particularly in the objectoriented toolkits. For example, the Amulet system supports both regular and selective undo (Myers Kosbie, 1996). A more theoretical treatment of the subject can be found in Thimbleby s (1990) book on User Interface Design. In addition, both reversibility and support for multiple potential interpretations were addressed in the work of Hudson Newell (1992) on probabilistic state machines for handling ....

Myers, B. A. & Kosbie, D. S. (1996), Reusable Hierarchical Command Objects, in Proceedings of ACM CHI'90.

....and then it could follow the arrows to determine that it could create the Chain description. The algorithm that Gamut uses to create new descriptions will be discussed below. 7.3. The Difference Between Events and Actions Both events and actions are derived from the Amulet command object [Myers and Kosbie 1996] data type. A command object represents a command such as one might find in the menubar. For instance, the standard cut, copy, and paste editing operations are implemented using command objects. Command objects are stored in widgets and input objects (called interactors ) and perform the work ....

Myers and Kosbie 1996 MYERS, B. A. AND KOSBIE, D. S. 1996. Reusable Hierarchical Command Objects. In Human Factors in Computing Systems, Proceedings SIGCHI'96, Denver, CO. pp. 260-267.

....in other ways. Indeed, the same framework has already been used to study the related issue of history mechanisms in hypertext systems and world wide web browsers [9] 1. 2 Undo linear and non linear The issue of undo in user interfaces has been studied by several authors over many years (e.g. [2, 15, 25, 22, 18]) Indeed, the ability to undo (not necessarily with an undo button) is seen as one of the key features of the direct manipulation paradigm [20] However, undo is far from a solved problem. Experiments have shown that even experienced users of word prcessors find it difficult to work out what ....

B. A. Myers and D. S. Kosbie. Reusable hierarchical command objects. In Proceedings of CHI 96, Vancouver, BC, Canada, pages 260--267. ACM Press, 1996.

....in interactive systems and helps shed light on the fundamental reflexive nature of undo. URL for related work: http: www.soc.staffs ac uk cmtajd topics undo 1 Introduction and background 1. 1 Undo The issue of undo in user interfaces has been studied by several authors over many years (e.g. [2, 13, 21, 19, 15]) This has included both work aimed at understanding the problem, and workon implementation structures. Despite this, experiments have shown that experienced users of Microsoft Word, which has a relatively simple and easy to use undo function, still have great difficulty in working out what undo ....

B. A. Myers and D. S. Kosbie. Reusable hierarchical command objects. In Proceedings of CHI 96, Vancouver, BC, Canada, pages 260--267. ACM Press, 1996.

No context found.

Myers, B.A. and Kosbie, D. "Reusable Hierarchical Command Objects," in CHI 1996. Vancouver, BC, Canada: pp. 260-267.

No context found.

Brad A Myers and David Kosbie. "Reusable Hierarchical Command Objects," Proceedings CHI'96: Human Factors in Computing Systems, Vancouver, BC, Canada, April 14-18, 1996a. pp. 260-267.

....and maintained by the system, to tie objects values together. Amulet and Garnet al..so include many other innovations, which are described in various papers [Myers 1989] Myers 1990a] Vander Zanden 1990] Myers 1991b] Myers 1991a] Hashimoto 1992] Myers 1994] Vander Zanden 1994] Vander Zanden 1995b] Myers 1996a] Myers 1996b] Myers 1998] This chapter concentrates on the prototype instance object systems in Garnet and Amulet. In Garnet s and Amulet s prototype instance object systems, there is no concept of a class since every object can serve as a prototype for other objects. Values of objects are ....

....the slots with a sequence of values, without any need for the object to even know it is being animated. Furthermore, Amulet s general undo facility takes advantage of this feature by remembering the old values of each changed object, and then just restoring the values if the user asks for an Undo [Myers 1996a] An interesting disadvantage of the prototype instance object system is that it is harder to see the specification of an object from the code. Slots can be added anywhere, and there is no clear declaration of the internal versus external slots in Garnet or Amulet. In the exported header ....

Brad A Myers and David Kosbie. "Reusable Hierarchical Command Objects," Proceedings CHI'96: Human Factors in Computing Systems, Vancouver, BC, Canada, April 14-18, 1996a. pp. 260-267.

....as for his or her selection handles and text input caret. Moreover, PebblesDraw supports both undo byuser and global undo functions. For example, when selecting undo by user, a user s previous command is undone, if possible. 3 Undo by user is implemented through a selective undo mechanism [6] provided by the underlying Amulet toolkit we developed (www.cs.cmu.edu amulet) and with which PebblesDraw was implemented. Laser pointers are a popular way to interact with presentations in meetings. Many systems provide computer recognition of the laser dot to control a PC s cursor, but ....

Myers, B. and Kosbie, D. Reusable hierarchical command objects. In Proceedings of CHI`96: Human Factors in Computing Systems (Vancouver, BC, Canada, Apr.). ACM Press, New York, 1996, 260--267.

....fuse users into thinking that they can only change the object s size from the handles that have their shape. Further studies of these issues are planned. Command Objects Rather than using a call back procedure as in other toolkits, Amulet al..locates a command object and calls its Do method [Myers 1996]. Amulet s commands also provide slots and methods to handle undo, selective undo and repeat, and enabling and disabling the command (graying it out) Command objects promote re use because commands for such high level behaviors as move object, create object, change property, become selected, cut, ....

....all the previous operations back to the beginning (like Microsoft Word version 6 and later) Amulet al..so supports a selective undo mechanism. Any previous command, including scrolling and selection operations, can be selectively undone, repeated on the same object, or repeated on a new selection [Myers 1996]. The Selective Undo method has an associated method which checks to see whether the command can still be executed. For example, if an operation changes the color of an item, the Selective Undo Allowed method will check to make sure that the object is still visible. If not, then the Selective Undo ....

[Article contains additional citation context not shown here]

Brad A Myers and David Kosbie. "Reusable Hierarchical Command Objects," Proceedings CHI'96: Human Factors in Computing Systems, Vancouver, BC, Canada, April 14-18, 1996. pp. 260-267.

....handle new example actions, hint highlighting, and guide objects. Furthermore, they must be able to generate the behaviors characteristic of board games like chains of relationships and a large number of modes. The Gamut s action language is based on the command object structure found in Amulet [14], the development environment in which Gamut has been implemented. A command object represents an atomic action such as Move, Create, Cut, Copy, and Paste. In Amulet, user actions are queued onto an undo history which Gamut uses as the input to the first phase of inferencing. First, the commands ....

B. A. Myers, D. S. Kosbie. Reusable Hierarchical Command Objects. Human Factors in Computing Systems, Proceeding SIGCHI'96, Denver, CO, April, 1996, pp 260-267.

....of restoring the old value. Since the undo mechanism can query and modify the data structures, and there is a standard protocol for most operations, often undo can be supplied by the library as well. For example, in Amulet, all the standard operations come with their own undo already supplied [19]. Automatic save and load of the application s data structures to files can be provided automatically if there is an open data model because the system can determine the relevant parts of the objects to store and retrieve. As discussed below, the current version of Java supports a partial open ....

....for operations that have been executed are available on the undo history list, and all potential commands and Interactors of an application can be found by investigating the objects attached to the application s windows. In Amulet, all high level operations are encapsulated into command objects [19]. In many other toolkits, when a widget like a button is used, the programmer must write a call back procedure (in Motif) or an event method (in Visual Basic) to handle the behavior. In Amulet, instead a command object is allocated, and its DO method is called. One result of the open data ....

Myers, B.A. and Kosbie, D. "Reusable Hierarchical Command Objects," in Proceedings CHI'96: Human Factors in Computing Systems. 1996. Vancouver, BC, Canada: pp. 260-267.

No context found.

MYERS, B.A. AND KOSBIE, D.S. 1997. Reusable hierarchical command objects. In Proceedings of CHI '97, 260-267.

No context found.

Myers, B., and Kosbie, D. Reusable Hierarchical Command Objects. In Proceedings of CHI `96.

First 50 documents

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC