Object-oriented programming for the Macintosh
Object-oriented programming for the Macintosh
Constraint-based tools for building user interfaces
ACM Transactions on Graphics (TOG) - Special issue on user interface software
A cookbook for using the model-view controller user interface paradigm in Smalltalk-80
Journal of Object-Oriented Programming
The NeXT book
Unidraw: a framework for building domain-specific graphical editors
ACM Transactions on Information Systems (TOIS)
Rendezvous: an architecture for synchronous multi-user applications
CSCW '90 Proceedings of the 1990 ACM conference on Computer-supported cooperative work
Graphical techniques in a spreadsheet for specifying user interfaces
CHI '91 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
The importance of pointer variables in constraint models
UIST '91 Proceedings of the 4th annual ACM symposium on User interface software and technology
Propagators and concurrent constraints
OOPSLA/ECOOP '90 Proceedings of the workshop on Object-based concurrent programming
An introduction to HITS: Human Interface Tool Suite
Intelligent user interfaces
An overview of GINA—the generic interactive application
UIMS Proceedings of the workshop on user interface management systems and environments on User interface management and design
Developing Software for the User Interface
Developing Software for the User Interface
User Interface Management Systems
User Interface Management Systems
Proceedings of the IFIP TC2/WG2.7 Working Conference on Engineering for Human-Computer Interaction
Developing applications with the Alpha UIMS
interactions
Hi-index | 0.00 |
A new mechanism based on taps is introduced to separate the output from the application code in graphical interactive interfaces. The mechanism is implemented in GINA, an object-oriented application framework. Taps maintain a functional mapping from application data to interface objects that is described in a general-purpose programming language. Taps are triggered automatically by user actions. Compared to constraints or the MVC model, taps do not need execution or memory support from the application objects, at the expense of a performance penalty. Screen updates, which pose the largest performance problem, are minimized by checking for attribute changes and window visibility. A comparison operation is used to maintain structural consistency between hierarchies of application and interface objects. Taps can be defined interactively using formulas in a spreadsheet-like tool.