| W. Buxton, M.R. Lamb, D. Sherman, and K.C. Smith. Towards a Comprehensive User Interface Management System. Computer Graphics, Proceedings SIGGRAPH'83, Detroit, Mich, July, 1983, pp. 35-42. |
....reusable presentation and interaction objects from a library [Myers 1987] In this way, applications could be tailored by user interface designers to apply a consistent set of rules across an environment of users. It remains to be seen whether the idea of user interface management systems [Buxton et al. 1983; Foley 1986] can be given new life in the context of object oriented programming. Summary There are very good traditional reasons for exploiting object oriented approaches in the development of o#ce information systems. Software reusability, maintainability and reliability are the main ....
W. Buxton, M.R. Lamb, D. Sherman and K.C. Smith, "Towards a Comprehensive User Interface Management System", Computer Graphics, vol. 17, no. 3, pp. 35-42, July 1983.
....overall environment. Section 4 provides an overview of the method that directs interface development, and the application development tools that support the method. Section 5 presents some conclusions. 2. Model Based User Interface Development Environments Early interactive design environments [3,12] provided programmers with a way of developing user interfaces semi automatically via a specification of the dialogue, or interactive behaviour, of the run time system. Although clearly superior to manual coding in a general purpose language, these systems generated rather crude interfaces, and ....
W. Buxton, M.R. Lamb, D. Sherman, and K.E. Smith, "Towards a comprehensive user interface management system", Computer Graphics, 17(3), 1983,pp. 35-42.
....set of tools that allows all aspects of a user interface to be specified pictorially. 2.1 Interface Builders There have been a large number of systems that allow users to select items from a pre defined library of widgets, and position them on the screen. Some of these, including Menulay [2], Trillium [7] DialogEditor [3] vu [40] Druid [41] Gilt [28] and the NeXT Interface Builder [35] provide a graphical editor that allows the position and size of each widget to be specified in a direct manipulation manner using a mouse. Often, these systems allow a few limited properties to ....
W. Buxton, M.R. Lamb, D. Sherman, and K.C. Smith. Towards a Comprehensive User Interface Management System. Computer Graphics, Proceedings SIGGRAPH'83, Detroit, Mich, July, 1983, pp. 35-42.
....layer is responsible for layout and device issues, the dialogue control defines the structure of the dialogue between the user and the application, and the application layer provides the functionality for the whole system. In the last several years, a large number of UIMS have been built [1, 14, 15, 9, 10, 5] and the issues involved in the architecture have become clearer. Serpent (Software Engineering Rapid Prototyping EnvironmenT) is a UIMS under development. It takes a particular view of some of these issues. This paper discusses the runtime architecture of Serpent and the model used within Serpent ....
Buxton, W., Lamb, M.R., Sherman, D., Smith, K.C. Toward a Comprehensive User Interface Management System. Computer Graphics 17(3), July, 1983.
....to create windows and dialog boxes. Examples include Visual Basic and the resource editors or constructors that come with Microsoft s Visual C and most other environments. Early research on this class of tools includes Trillium from Xerox PARC [15] and MenuLay from the University of Toronto [6]. The idea was refined by Jean Marie Hullot while a researcher at INRIA, and Hullot later brought the idea with him to NeXT, which popularized this type of tool with the NeXT Interface Builder. An important reason for the success of interface builders has been that they use graphical means to ....
Buxton, W., et al. "Towards a Comprehensive User Interface Management System," in Proceedings SIGGRAPH'83: Computer Graphics. 1983. Detroit, Mich: 17. pp. 35-42.
....these systems may generate code that is compiled and linked with the rest of the application or they may generate some type of internal representation that a User Interface Management System s (UIMS) run time system can use to implement the UI when the target application is executed. MENULAY [Buxton 1983] was one of the first interactive UI builders and was part of an early UIMS. It was used for laying out networks of menus that could be structured in a hierarchic manner. It allowed the designer to assign function names to be called on menu selections and to set object properties, such as ....
W. Buxton, M.R. Lamb, D. Sherman and K.C. Smith. "Towards a Comprehensive User Interface Management System," Computer Graphics. Proceedings of SIGGRAPH '83. 17(3): pp. 35-42, July, 1983.
....reusable presentation and interaction objects from a library [Myers 1987] In this way, applications could be tailored by user interface designers to apply a consistent set of rules across an environment of users. It remains to be seen whether the idea of user interface management systems [Buxton et al. 1983; Foley 1986] can be given new life in the context of object oriented programming. 12 Integrated Office Systems 6 Summary There are very good traditional reasons for exploiting object oriented approaches in the development of office information systems. Software reusability, maintainability and ....
W. Buxton, M.R. Lamb, D. Sherman and K.C. Smith, "Towards a Comprehensive User Interface Management System", Computer Graphics, vol. 17, no. 3, pp. 35-42, July 1983.
....UIDEs and user oriented design of user interfaces User interface management systems (UIMSs) have gradually become a focal point of research in software engineering and human computer interaction since they first emerged early in the last decade. The earliest examples of UIMSs (e.g. Menulay [4]) provided run time support for user computer interaction, but little else. A major aim was to facilitate the prototyping of user interfaces, but minimal assistance was given to the unfortunate interface designer, who was generally obliged to describe the appearance and behaviour of the interface ....
W. Buxton, M. R. Lamb, D. Sherman and K. C. Smith, Towards a Comprehensive User Interface Management System, ACM Computer Graphics, Vol. 17, No. 3, 1983, pp 45-42.
....mouse. The Steamer project at BBN (1979 85; ONR funding) demonstrated many of the ideas later incorporated into interface builders and was probably the first object oriented graphics system. Trillium [12] was developed at Xerox PARC in 1981. Another early interface builder was the MenuLay system [5] developed by Bill Buxton at the University of Toronto (1983, funded by the Canadian Government) The Macintosh (1984) included a Resource Editor which allowed widgets to be placed and edited. Jean Marie Hullot created SOS Interface in Lisp for the Macintosh while working at INRIA (1984, ....
Buxton, W., et al. "Towards a Comprehensive User Interface Management System," in Proceedings SIGGRAPH'83: Computer Graphics. 1983. Detroit, Mich. 17. pp. 35-42.
No context found.
W. Buxton, M.R. Lamb, D. Sherman, and K.C. Smith. Towards a Comprehensive User Interface Management System. Computer Graphics, Proceedings SIGGRAPH'83, Detroit, Mich, July, 1983, pp. 35-42.
No context found.
Buxton, W., Lamb, M.R., Sherman, D., and Smith, K.C., Towards a Comprehensive User Interface Management System, in Proc. of ACM Conf. on Computer Graphics SIGGRAPH'83 (Detroit, 25-29 July 1983.
No context found.
W. Buxton et al. Towards a Comprehensive User Interface Management System. In Proc. SIGGRAPH '83, pages 35--42, 1983.
No context found.
W. Buxton, M.R. Lamb, D. Sherman and K.C. Smith, "Towards a Comprehensive User Interface Management System", Computer Graphics, vol. 17, no. 3, pp. 35-42, July 1983.
No context found.
W. Buxton, M. Lamb, D. Sheman, K. Smith. Towards a comprehensive user interface management system. In Proceedings of SIGGRAPH'83. 1983.
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