Standardizing the interface between applications and UIM's

ABSTRACT

The user interface building blocks of any User Interface Management System (UIMS) have built-in assumptions about what information about application programs they need, and assumptions about how to get that information. The lack of a standard to represent this information leads to a proliferation of different assumptions by different building blocks, hampering changeability of the user interface and portability of applications to different sets of building blocks. This paper describes a formalism for specifying the information about applications needed by the user interface building blocks (i.e. the UIMS/Application interface) so that all building blocks share a common set of assumptions. The paper also describes a set of user interface building blocks specifically designed for these standard UIMS/Application interfaces. These building blocks can be used to produce a wide variety of user interfaces, and the interfaces can be changed without having to change the application program.

REFERENCES

• 1: J. Foley , C. Gibbs , S. Kovacevic, A knowledge-based user interface management system, Proceedings of the SIGCHI conference on Human factors in computing systems, p.67-72, May 15-19, 1988, Washington, D.C., United States [doi>10.1145/57167.57178]
• 2: M. Green. Report on dialogue specification tools. In G. E. Pfaff, editor, User In2erface Management Systems, pages 9-20. Springer-Verlag, 1983.
• 3: Philip J. Hayes , Pedro A. Szekely , Richard A. Lerner, Design alternatives for user interface management sytems based on experience with COUSIN, Proceedings of the SIGCHI conference on Human factors in computing systems, p.169-175, April 1985, San Francisco, California, United States
• 4: Kerry Kimbrough , LaMott Oren, Clue: a common lisp user interface environment, Proceedings of the 1st annual ACM SIGGRAPH symposium on User Interface Software, p.85-94, October 17-19, 1988, Alberta, Canada [doi>10.1145/62402.62416]
• 5: Glenn E. Krasner , Stephen T. Pope, A cookbook for using the model-view controller user interface paradigm in Smalltalk-80, Journal of Object-Oriented Programming, v.1 n.3, p.26-49, Aug./Sept. 1988
• 6: Henry Lieberman, There's more to menu systems than meets the screen, ACM SIGGRAPH Computer Graphics, v.19 n.3, p.181-189, Jul. 1985
• 7: Joel McCormack , Paul Asente, An overview of the X toolkit, Proceedings of the 1st annual ACM SIGGRAPH symposium on User Interface Software, p.46-55, October 17-19, 1988, Alberta, Canada [doi>10.1145/62402.62407]
• 8: B. A. Myers, Encapsulating interactive behaviors, Proceedings of the SIGCHI conference on Human factors in computing systems: Wings for the mind, p.319-324, March 1989
• 9: Brad A. Myers, User-Interface Tools: Introduction and Survey, IEEE Software, v.6 n.1, p.15-23, January 1989 [doi>10.1109/52.16898]
• 10: Kurt J. Schmucker, Object-oriented programming for the Macintosh, Hayden Books, Carmel, IN, 1986
• 11: Andrew J. Schulert , George T. Rogers , James A. Hamilton, ADM — a dialog manager, Proceedings of the SIGCHI conference on Human factors in computing systems, p.177-183, April 1985, San Francisco, California, United States
• 12: R. Smith, G. Lafue, and S. Vestal. Declarative task description as a user-interface structuring mechanism. Computer. pages 29-38, September 1984.
• 13: Pedro Alejandro Szekely, Separating the user interface from the functionality of application programs, 1987