Smalltalk-80: the language and its implementation
Smalltalk-80: the language and its implementation
The C++ programming language
Using prototypical objects to implement shared behavior in object-oriented systems
OOPLSA '86 Conference proceedings on Object-oriented programming systems, languages and applications
Common LISP: the language
A programmer's guide to object-oriented programming in Common LISP
A programmer's guide to object-oriented programming in Common LISP
Xlib programming manual (3rd ed.)
Xlib programming manual (3rd ed.)
Xlib reference manual (3rd ed.)
Xlib reference manual (3rd ed.)
Modular implementation of presentations
CHI '87 Proceedings of the SIGCHI/GI Conference on Human Factors in Computing Systems and Graphics Interface
There's more to menu systems than meets the screen
SIGGRAPH '85 Proceedings of the 12th annual conference on Computer graphics and interactive techniques
Presentation Based User Interfaces
Presentation Based User Interfaces
Creating user interfaces by demonstration
Creating user interfaces by demonstration
Communications of the ACM - Special issue on LISP
EmbeddedButtons: documents as user interfaces
UIST '91 Proceedings of the 4th annual ACM symposium on User interface software and technology
A guided tour of the Common Lisp interface manager
ACM SIGPLAN Lisp Pointers
EmbeddedButtons: supporting buttons in documents
ACM Transactions on Information Systems (TOIS) - Special issue on user interface software and technology
User interface development and software environments: the Chiron-1 system
ICSE '91 Proceedings of the 13th international conference on Software engineering
Media-independent interfaces in a media-dependent world
COOTS'95 Proceedings of the USENIX Conference on Object-Oriented Technologies on USENIX Conference on Object-Oriented Technologies (COOTS)
| Hi-index | 0.00 |
We describe a system for associating the user interface entities of an application with their underlying semantic objects. The associations are classified by arranging the user interface entities in a type lattice in an object-oriented fashion. The interactive behavior of the application is described by defining application operations in terms of methods on the types in the type lattice. This scheme replaces the usual “active region” interaction model, and allows application interfaces to be specified directly in terms of the objects of the application itself. We discuss the benefits of this system and some of the difficulties we encountered.