A knowledge-based user interface management system
CHI '88 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
The Xerox Star: A Retrospective
Computer
Standardizing the interface between applications and UIM's
UIST '89 Proceedings of the 2nd annual ACM SIGGRAPH symposium on User interface software and technology
Automatic, look-and-feel independent dialog creation for graphical user interfaces
CHI '90 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Making usable, useful, productivity-enhancing computer applications
Communications of the ACM
Twinkling lights and nested loops: distributed problem solving and spreadsheet development
International Journal of Man-Machine Studies - Computer-supported cooperative work and groupware. Part 1
Frameworks for interactive, extensible, information-intensive applications
UIST '92 Proceedings of the 5th annual ACM symposium on User interface software and technology
ACE: building interactive graphical applications
Communications of the ACM - Special issue on graphical user interfaces
Programming the multimodal interface
MULTIMEDIA '93 Proceedings of the first ACM international conference on Multimedia
Encapsulating knowledge for intelligent automatic interaction objects selection
CHI '93 Proceedings of the INTERACT '93 and CHI '93 Conference on Human Factors in Computing Systems
Automatic generation of task-oriented help
Proceedings of the 8th annual ACM symposium on User interface and software technology
A GUI on top of a functional language (poster)
ICFP '97 Proceedings of the second ACM SIGPLAN international conference on Functional programming
Improving mobile internet usability
Proceedings of the 10th international conference on World Wide Web
COMET(s), A Software Architecture Style and an Interactors Toolkit for Plastic User Interfaces
Interactive Systems. Design, Specification, and Verification
Hi-index | 0.00 |
Most UI toolkits and UIMSs make use of widgets, e.g., buttons, text fields, sliders, menus. Designers construct user interfaces by choosing and laying out widgets, then connectimg them to application semantics. This approach has four problems. First, most widgets are too low-level; constructing interfaces from them takes too much work. Second, working with widgets focuses attention on appearance and layout issues, rather than on more important semantic design issues. Third, designers can easily make poor widget choices, yielding poor interfaces. Fourth, widgets do not mesh well with application semantics; they know nothing about the variables they control. We are developing an application construction environment in which designers and implementers work with semantic-based controls called Selectors rather than with widgets. Selectors are classified according to their interface semantics (e.g., mutually-exclusive choice), rather than their appearance. Each type of Selector can be presented in a variety of ways; this may be chosen semi-automatically. Selectors mesh well with application semantics: their values are application data-types and their views determine how to present valid values automatically.