This article proposes and tests a two-component model for describing and programming the finegrained aspects of non-WIMP interaction. The model combines a data-flow or constraint-like component for the continuous relationships with an event-based component for discrete interactions, which can enable or disable individual continuous relationships. Its key ingredients are the separation of non-WIMP interaction into two components and the framework it provides for communication between the two

A direct manipulation user interface presents a set of visual representations on a display and a repertoire of manipulations that can be performed on any of them. Such representations might include screen buttons, scroll bars, spreadsheet cells, or flowchart boxes. Interaction techniques of this kind were first seen in interactive graphics systems; they are now proving effective in user interfaces for applications that are not inherently graphical. While they are often easy to learn and use, these interfaces are also typically difficult to specify and program clearly. Examination of

A user interface software tool helps developers design and implement the user interface. Research on past tools has had enormous impact on today's developers---virtually all applications today were built using some form of user interface tool. In this paper, we consider cases of both success and failure in past user interface tools. From these cases we extract a set of themes which can serve as lessons for future work. Using these themes, past tools can be characterized by what aspects of the user interface they addressed, their threshold and ceiling, what path of least resistance they offer, how predictable they are to use, and whether they addressed a target that became irrelevant. We believe the lessons of these past themes are particularly important now, because increasingly rapid technological changes are likely to significantly change user interfaces. We are at the dawn of an era where user interfaces are about to break out of the "desktop" box where they have been stuck for the ...

this paper is the concise study of the need for a CAS user interface. Furthermore, it represents an important and prior step to any effective realization. 2 Description of the existing user interfaces

this paper is to describe the design and implementation of a portable user interface toolkit named IUP/LED. IUP/LED is portable to many different computer environments, and our experience indicates it is easily used by both programmers and end users. The main characteristics of IUP/LED are:

A user interface description is an abstract model that is used to describe the structure of a dialogue between a user and an interactive computer system. It forms the basis of notation that are used in user interface management systems. In this paper three classes of description formalisms are investigated. These classes are single-threaded representations (state-transition-diagram and grammar based specifications), multi-threaded representation (events, state charts based specifications) and concurrent dialogue representations (Petri nets and Process Calculus based specifications). Formal definitions of all the models are presented along-with algorithms for converting the notions into executable forms, which are used in various User Interface Management Systems. An evaluation method is presented and the implication of the results for the design and implementation of UIMs are also discussed. i Contents 1 Introduction 1 2 Description Formalisms 1 2.1 Single-threaded description form...

The goal of this research is to propose a software architecture of window systems that facilitate cooperative processing among graphical user interface (GUI) applications, and to implement a window system called BTRON2 window system based on the architecture. Recently, cooperation of GUI applications with other external programs is of much interest because of several reasons. First, the cooperation is necessary for supporting distributed GUI applications in distributed environments, which include Groupware and distributed implementation of GUI applications. Second, cooperation among conventional GUI applications is effective to give them high inter-operability. Application cooperation and tool integration are the topics of this issue. Lastly, dynamic integration of GUI applications with other programs by users increases extensibility and customizability of the GUI applications. This issue includes script processing and assistive technology that dynamically extends or customizes user in...

If the interface of a system is to be made completely adaptable to the current user, then the interface and application have to be completely separate. Furthermore, if the model of the interface is independent of both the application and the operating system, then the user will be able to have their own model of the interface, which when added to the application, creates the working system. In this paper, we put forward an architecture to facilitate this goal. INTRODUCTION An adaptive system is a system "which automatically acquires knowledge about its users, updates this knowledge over time, and uses the knowledge to adapt to the users' requirements" [11]. The key part of this definition is that adaption is an automatic process, instigated by the system as opposed to the user. If a system is to change its interface in fundamental ways (for example, more than simply changing window sizes or colours), then the system will have to be based on an architecture where the model of the inter...

: The separation of the user interface portion of a software system from the functional portion is intended to enable the production of tools to deal with the user interface, and to raise the quality and modularity of resulting software systems. One class of such separation tools that have been developed is the User Interface Management System (UIMS). This paper describes the runtime architecture and dialogue model of a particular UIMS named Serpent. Serpent uses existing software systems to create a UIMS based on a structured production model to specify the dialogue, and uses a database approach for communication between its internal layers. The model for the dialogue in Serpent supports simultaneity of subdialogues and presents the dialogue specifier with a model that views data as mapping from the application to the presentation. The database approach for communication between the layers provides a model that application programmers understand well and find easy to use. ...

this document, published December 1991, represents the results of discussions held at various NIST ISEE workshops and comments provided by the participants of these workshops, as well as a review by the members of TC33/TGRM. During 1992, a Reference Model Change Control Board, consisting of members of TGRM and the NIST ISEE working group, met several times to prepare this third edition of this document in response to receipt of approximately 200 requested changes. The U.S. Navy's NGCR PSESWG program was particularly helpful in pointing out issues that needed clarification. Major changes for this third edition include the addition of operating system services, enhanced user interface services, a rewritten policy enforcement clause, and replacement of the graphic describing the model. This report is published jointly as an ECMA Technical Report and a NIST Special Publication. Accepted as an ECMA Technical Report by the General Assembly of June, 1993 (tentative). Certain commercial products are identified in this report. Such identification does not imply recommendation or endorsement by the National Institute of Standards and Technology, nor does it imply that the product, publication, or service identified is necessarily the best available for the purpose. Draft November 24, 1993 Edition v Table of Contents Section I. Software Engineering Environment Frameworks 1 1 Scope 1