A tour of suite user interface software
UIST '90 Proceedings of the 3rd annual ACM SIGGRAPH symposium on User interface software and technology
CLIM: the Common Lisp interface manager
Communications of the ACM - Special issue on LISP
The PICASSO applications framework
UIST '91 Proceedings of the 4th annual ACM symposium on User interface software and technology
Separating application code from toolkits: eliminating the spaghetti of call-backs
UIST '91 Proceedings of the 4th annual ACM symposium on User interface software and technology
Transportable Applications Environment (TAE) Plus user interface designer WorkBench
CHI '92 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
The abstraction-link-view paradigm: using constraints to connect user interfaces to applications
CHI '92 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
The AT&T display construction set user interface management system (UIMS)
CHI '92 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
INCENSE: A system for displaying data structures
SIGGRAPH '83 Proceedings of the 10th annual conference on Computer graphics and interactive techniques
Chimera: hypertext for heterogeneous software environments
ECHT '94 Proceedings of the 1994 ACM European conference on Hypermedia technology
Design of GUIs from a programming perspective
TRI-Ada '94 Proceedings of the conference on TRI-Ada '94
A concurrency analysis tool suite for Ada programs: rationale, design, and preliminary experience
ACM Transactions on Software Engineering and Methodology (TOSEM)
Graph models for reachability analysis of concurrent programs
ACM Transactions on Software Engineering and Methodology (TOSEM)
Chiron-1: a software architecture for user interface development, maintenance, and run-time support
ACM Transactions on Computer-Human Interaction (TOCHI)
A component- and message-based architectural style for GUI software
Proceedings of the 17th international conference on Software engineering
Developing applications with the Alpha UIMS
interactions
Requirements for a layered software architecture supporting cooperative multi-user interaction
Proceedings of the 18th international conference on Software engineering
Lessons on converting batch systems to support interaction: experience report
ICSE '97 Proceedings of the 19th international conference on Software engineering
SAAM: a method for analyzing the properties of software architectures
ICSE '94 Proceedings of the 16th international conference on Software engineering
Opossum: a flexible schema visulaization and editing tool
CHI '94 Conference Companion on Human Factors in Computing Systems
Model-view-controller and object teams: a perfect match of paradigms
Proceedings of the 2nd international conference on Aspect-oriented software development
HERCULE: Non-invasively Tracking JavaTM Component-Based Application Activity
ECOOP '00 Proceedings of the 14th European Conference on Object-Oriented Programming
Hi-index | 0.00 |
The development of user interfaces for large applications is subject to a series of well-known problems including cost, maintainability, and sensitivity to changes in the operating environment. The Chiron user interface development system has been built to address these software engineering concerns. Chiron introduces a series of layers that insulate components of an application from other components that may experience change. To separate application code from user interface code, user interface agents called artists are attached to application abstract data types. Operations on abstract data types within the application implicitly trigger user interface activities. Chiron also provides insulation between the user interface layer and the underlying system; artist code is written in terms of abstract depiction libraries that insulate the code from the specifics of particular windowing systems and toolkits. Concurrency is pervasive in the Chiron architecture. Inside an application there can be multiple execution threads; there is no requirement for a user interface listening/dispatching routine to have exclusive control. Multiple artists can be attached to a single application abstract data type, providing alternative forms of access by a single user or coordinated access and manipulation by multiple users.