| Myers B, McDaniel R., Mickish A., Klimovitski A. (1995) "The Design for the Amulet User Interface Toolkit." Proc. Human-Computer Interaction Consortium meeting. |
....Keywords: User interface software, graphical toolkits, declarative GUI language, brick object model, hyperdocument, interaction control, ubiquitous components, multiple views. 1 INTRODUCTION It is a well known fact that user interfaces are not only hard to design but are also hard to implement (Myers, 1995). As a consequence, most people prefer using tools (such as interactive interface builders or other kinds of user interface management systems) rather than programming directly with a GUI toolkit. Thus, in recent years, attention has rather been focused on tools than on the principles of GUI ....
....differ one from another. Thus, the ability of customizing objects without having to create new classes is a feature that is especially well suited for GUI design. This point was formerly addressed in some research systems through the concept of prototype instance object systems such as Amulet (Myers 1995). 4 THE PSEUDO DECLARATIVE API Ubit provides two compatible C APIs. The first one is a classical object oriented API: object are created by invoking the new primitive and are added to parents by using their add method. One could for instance write the following source code to create a push ....
Myers B, McDaniel R., Mickish A., Klimovitski A. (1995) "The Design for the Amulet User Interface Toolkit." Proc. Human-Computer Interaction Consortium meeting.
....code is rather compact and (relatively) easy to understand. This last point explains the success of this system and shows that visual systems do not have the exclusivity of simplicity: textual languages can also be pretty convenient to use if well designed and well suited to the domain. Amulet [6] is based on an object oriented language which is written on the top of C . Once again, this specialized language provides simpler, better adapted and more powerful specifications to program the Amulet toolkit than a classical C or C interface would do. Furthermore, a major advantage of this ....
....time. To paraphrase a quotation from [9] this means that we can both benefit from the intuitiveness but (relatively) low expressivity of interface builders and the low intuitiveness but high level of expressivity of standard programming languages. Other systems (for instance the Amulet [6] system) also provide a special purpose language written on the top of a standard language. But, as said before, XXL is not only a textbased solution but also provides true equivalence between textual and visual descriptions. Conversely, FormsVBT [1] which is one of the few systems that are also ....
Myers B, McDaniel R., Mickish A., Klimovitski A., The Design for the Amulet User Interface Toolkit.. Proc. Human-Computer Interaction Consortium meeting, Feb. 1995.
....interfaces are characterized by bursts of tight, high volume, feedback intensive, input output event sequences, and these sequences can be described by patterns. To represent lexical patterns, we pull ideas from object oriented UI toolkits. Object oriented toolkits like Garnet [13] and Amulet [16] provide interactors that encapsulate these tight input output protocols into implemented units that may be selected from a library and specialized to a particular use. In both toolkits, the number of interactors is fixed and relatively small. The MASTERMIND Interaction Model is an abstraction of ....
Myers B., McDaniel R., Mickish A., Klimovitski A.. The Design for the Amulet User Interface Toolkit. Human Computing Interaction Consortium. 1995.
No context found.
Myers B, McDaniel R., Mickish A., Klimovitski A., The Design for the Amulet User Interface Toolkit , proc. HumanComputer Interaction Consortium meeting, February, 1995.
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