Showing papers on "User interface published in 1988"

A cookbook for using the model-view controller user interface paradigm in Smalltalk-80

Abstract: A switch actuating device adapted for conjoint rotation with a rotatable assembly of a prime mover. Means for mounting to the rotatable assembly so as to be conjointly rotatable therewith includes a pair of sets of opposite surfaces, and switch operating means conjointly rotatable with the mounting means is arranged for axial movement thereon between a pair of opposite positions. A pair of centrifugal weight members are responsive to the rotational speed of the device to effect the axial movement of the switch operating means between its opposite positions and include a pair of sets of means arranged for guiding engagement on the oppposite surface set pair upon the axial movement of the switch operating means between its opposite positions, respectively. A pair of springs are respectively biased between the centrifugal members. A method of assembling a switch actuating device is also disclosed.

User interface with multiple workspaces for sharing display system objects

Abstract: Workspaces provided by an object-based user interface appear to share windows and other display objects. Each workspace's data structure includes, for each window in that workspace, a linking data structure called a placement which links to the display system object which provides that window, which may be a display system object in a preexisting window system. The placement also contains display characteristics of the window when displayed in that workspace, such as position and size. Therefore, a display system object can be linked to several workspaces by a placement in each of the workspaces' data structures, and the window it provides to each of those workspaces can have unique display characteristics, yet appear to the user to be the same window or versions of the same window. As a result, the workspaces appear to be sharing a window. Workspaces can also appear to share a window if each workspace's data structure includes data linking to another workspace with a placement to the shared window. The user can invoke a switch between workspaces by selecting a display object called a door, and a back door to the previous workspace is created automatically so that the user is not trapped in a workspace. A display system object providing a window to a workspace being left remains active so that when that workspace is reentered, the window will have the same contents as when it disappeared. Also, the placements of a workspace are updated so that when the workspace is reentered its windows are organized the same as when the user left that workspace. The user can enter an overview display which shows a representation of each workspace and the windows it contains so that the user can navigate to any workspace from the overview.

Intermedia: the concept and the construction of a seamless information environment

Abstract: A description is given of Intermedia, a tool designed to support both teaching and research in a university environment. This multiapplication hypermedia system provides linking capabilities integrated into a desktop user environment. Hypermedia is simply an extension of hypertext that incorporates other media in addition to text. To promote consistency, the applications were built with an object-oriented framework. A sample Intermedia session is presented. >

Finding facts vs. browsing knowledge in hypertext systems

Abstract: The authors discuss the role of information retrieval, interface design, and cognitive science in hypertext research. They present a user-centered framework for information-seeking that has been used in evaluating two hypertext systems. They apply the framework to key design issues related to information retrieval in hypertext systems. >

Searching for information in a hypertext medical handbook

Abstract: Medicine is an ideal domain for hypertext applications and research. Implementing a popular medical handbook in hypertext underscores the need to study hypertext in the context of full-text document retrieval, machine learning, and user interface issues.

Towards a Practical GOMS Model Methodology for User Interface Design

Abstract: Publisher Summary This chapter presents a practical GOMS model methodology for user interface design. The basic approach to user-interface design using the cognitive complexity approach would be that the iterative design process would be followed, but with the evaluation of a proposed design being done with simulation techniques rather than actual human user testing; only a final test of the design would require actual user testing. Additional user testing would be involved to develop aspects of the design, such as screen layout, that are not directly addressed by an analysis of the procedures entailed by the design. There are several problems in using the cognitive complexity approach as a design tool that have become clear from technology transfer. The chapter presents two critical problems: (1) the difficulty of constructing production rule simulation models, and (2) the difficulty of doing, in a standardized and reliable way, the detailed task analysis required to construct the representation of the procedural knowledge that the user should have to operate the system.

System for random access to an audio video data library with independent selection and display at each of a plurality of remote locations

Abstract: Adapted for use in hotels, hospitals, and similar environments, the disclosed system allows numerous system users to operate user terminals at any of a plurality of locations to access a common library of audio-video data contained on a collection of record items such as, video tape cartridges, stored in a housing located at a remote central location. Using a computer controlled filer, the system retrieves a data record item from an array of housing storage sites at each user's request, loading the same into one of a plurality of playback devices also located at the central location, from which the audio video signal is directed to the user's terminal for readout. Each user may also access local television, radio, satellite video, and any other optional signal source connected to the system. System software running on a system supervisor computer processes user requests and controls the filer and the play back devices, while customized software that runs on each user terminal provides a user interface for interacting with the system supervisor computer. A multifrequency signal modulator and combiner system allows tuning of each user terminal to the signal from a particular play back device.

Interface metaphors and user interface design

Abstract: Publisher Summary This chapter discusses interface metaphors and the user interface design. The integration of operational, structural, and pragmatic approaches to metaphors can provide guidance and a starting point for the design of a user interface that integrates a central metaphor, with a carefully analyzed similarity basis and a set of planned mismatches, with myriad other interface elements that support and exploit the matches and mismatches inhering in the metaphor. Metaphoric comparisons and interface presentations do more than render static denotative correspondences. They have motivational and affective consequences for users. They interact with and frame users' problem-solving efforts in learning about the target domain. Metaphors have been employed to increase the initial familiarity of the target domain, but they have an inevitable further role to play. The ultimate problem that the user should solve is to develop an understanding of the target domain itself—a mental model. Interface metaphors should also be viewed as tools proffered to users for articulating mental models.

Creating user interfaces by demonstration

Abstract: When creating highly-interactive, Direct Manipulation interfaces, one of the most difficult design and implementation tasks is handling the mouse and other input devices. Peridot, a new User Interface Management System, addresses this problem by allowing the user interface designer to demonstrate how the input devices should be handled by giving an example of the interface in action. The designer uses sample values for parameters, and the system automatically infers the general operation and creates the code. After an interaction is specified, it can immediately be executed and edited. This promotes extremely rapid prototyping since it is very easy to design, implement and modify mouse-based interfaces. Peridot also supports additional input devices such as touch tablets, as well as multiple input devices operating in parallel (such as one in each hand) in a natural, easy to specify manner. This is implemented using active values, which are like variables except that the objects that depend on active values are updated immediately whenever they change. Active values are a straightforward and efficient mechanism for implementing dynamic interactions.

Virtual and emulated objects for use in the user interface of a display screen of a display processor

Abstract: A user interface is represented on the display screen in the form of metaphoric objects, called icons, with which the user can interact by changing the input focus to a designated object by visually pointed to it via the input means, which thereafter permits manipulation of the designated object or interaction with data input/output relative to the designated object. This input means is also used to initially change the input focus to either the allocated emulating processor screen portion or to the remaining portion of the central processor display screen prior to interaction with the metaphoric objects in a selected screen portion, the change of the input focus causing subsequent user input via the input means to be directed to the selected screen portion until interrupted by a change in focus input to the other of the screen portions by the user via the input means. An icon may be a representation of a virtual object, such as a virtual floppy disk, that is accessible in either the host system world or in the emulating processor world even though the virtual floppy disk may have a filing system alien to the host system world.

ET++—an object oriented application framework in C++

Abstract: ET++ is an object-oriented application framework implemented in C++ for a UNIX† environment and a conventional window system. The architecture of ET++ is based on MacApp and integrates a rich collection of user interface building blocks as well as basic data structures to form a homogeneous and extensible system. The paper describes the graphic model and its underlying abstract window system interface, shows composite objects as a substrate for declarative layout specification of complex dialogs, and presents a model for editable text allowing the integration of arbitrary interaction objects.

Human-computer interface design

Abstract: User psychology interface analysis and specification theoretical approaches dialogue design presentation design data entry interfaces data display and data retrieval interfaces development of human-computer interfaces

ConMan: a visual programming language for interactive graphics

Abstract: Traditionally, interactive applications have been difficult to build, modify and extend. These integrated applications provide bounded bounded functionality, have a single thread of control and a fixed user interface that must anticipate everything the user will need.Current workstations allow several processes to share the screen. With proper communication between processes, it is possible to escape previous models for application development and evolution.ConMan is a high-level visual language we use on an IRIS workstation that lets users dynamically build and modify graphics applications. To do this, a system designer disintegrates complex applications into modular components. By interactively connecting simple components, the user constructs a complete graphics application that matches the needs of a task. A connection manager controls the flow of data between individual components. As a result, we replace the usual user-machine dialog with a dynamic live performance that is orchestrated by the user.

Procedure for automatically customizing the user interface of application programs

Abstract: An application program automatically creates and presents a customized user interface. This is done by determining a set of operations which is appropriate for the current user based on various relevant characteristics of the user. The application program presents only the specified operations in the menus, icons, application bars or other interface components of the application program.

Cost/benefit analysis for incorporating human factors in the software lifecycle

Abstract: New software engineering techniques and the necessity to improve the user interface in increasingly interactive software environments have led to a change in traditional software development methods. Methodologies for improvement of the interface design, an overview of the human factors element, and cost/benefit aspects are explored.

Building user interfaces by direct manipulation

Abstract: User interfaces based on mice, bitmap displays and windows are becoming commonplace, and there are guidelines on how such interfaces should function [Apple 85]. As a consequence, there is a growing expectation that all programs, no matter how trivial or how complicated, should present a graphically elegant and sophisticated user interface.

The Rapport multimedia conferencing system-a software overview

Abstract: The Rapport multimedia conferencing system supports interactive, real-time, distributed conferences among two or more people. Executing on personal workstations interconnected by data and voice networks, Rapport provides basic mechanisms to create, manage, and terminate conferences. The authors focus on the Rapport software, which is a three-level hierarchy comprised of the user interface, conference server, and system levels. The user interface level provides humans and other programs with access to the Rapport system. Maintaining consistent views of the conference for all the participants, the conference server level coordinates the activities of the conferees and provides basic protocols for exchanging information and control during a conference. The system level includes window management service and drivers for the hardware required to transmit data in the various media. >

Modeling the user in natural language systems

Abstract: For intelligent interactive systems to communicate with humans in a natural manner, they must have knowledge about the system users. This paper explores the role of user modeling in such systems. It begins with a characterization of what a user model is and how it can be used. The types of information that a user model may be required to keep about a user are then identified and discussed. User models themselves can vary greatly depending on the requirements of the situation and the implementation, so several dimensions along which they can be classified are presented. Since acquiring the knowledge for a user model is a fundamental problem in user modeling, a section is devoted to this topic. Next, the benefits and costs of implementing a user modeling component for a system are weighed in light of several aspects of the interaction requirements that may be imposed by the system. Finally, the current state of research in user modeling is summarized, and future research topics that must be addressed in order to achieve powerful, general user modeling systems are assessed.

What is an Expert System

Abstract: Expert systems are probably the predominant area of artificial intelligence (AI) since the technology has a wide degree of application today. Expert systems function primarily on the concept of 'if - then -' rules. For example, if the soil water content for a particular crop is at a critical water level and there is no anticipated rainfall for several days, then irrigate. One of the unique characteristics of expert systems is the ability to arrive at a decision without complete information and then justify the decision. The decision may even have a certainty level associated with it. This paper discusses expert system components including the knowledge base, the inference engine, user interface, and knowledge acuisition, advantages and disadvantages of expert systems.

Stepwise refinement and verification in box-structured systems

Abstract: The author proposes that the formality of specifications and designs be developed together in box structures with many sponsor and user interfaces. Box structures of data abstractions allow the stepwise refinement and verification of hierarchical system designs from their specifications at formal and informal levels. He discusses the features and advantages of the approach. He used a navigation and weather buoy case study and gives a detailed, step-by-step application of the method. >

A tool for integrating conceptual schemas and user views

Abstract: An interactive tool has been developed to assist database designers and administrators (DDA) in integrating schemas. It collects the information required for integration from a DDA, performs essential bookkeeping, and integrates schemas according to the semantics provided. The authors present the capabilities of this tool by discussing the integration methodology and the user interface of the tool. >

The transparent PROLOG machine (TPM): an execution model and graphical debugger for logic programming

Abstract: An augmented and ⧸ or tree representation of logic programs is presented as the basis for an advanced graphical tracing and debugging facility for PROLOG. An extension of our earlier work on “retrospective zooming”, this representation offers several distinct advantages over existing tracing and debugging facilities: (1) it naturally incorporates traditional and ⧸ or trees and Byrd box models (call⧸exit⧸fail⧸redo procedural models) as special cases; (2) it can be run in slow-motion, close-up mode for novices or high-speed, long-distance mode for experts with no attendant conceptual change; (3) it serves as the uniform basis for textbook material, video-based teaching material, and an advanced user interface for experienced PROLOG programmers; (4) it tells the truth about clause head matching and deals correctly with the cut. One of the key insights underlying the work is the realization that it is possible to display an execution space of several thousand nodes in a meaningful way on a modern graphics workstation. By enhancing and ⧸ or trees to include “status boxes” rather than simple “nodes”, it is possible to display both a long-distance view of execution and the full details of clause-head matching. Graphical “collapsing” techniques enable the model to deal with user-defined abstractions, higher-order predicates such as setof, and definite-clause grammars. The current implementation runs on modern graphics workstations and is written in PROLOG.

A taxonomy of window manager user interfaces

Abstract: A taxonomy for the user-visible parts of window managers is presented. It is noted that there are actually very few significant differences, and the differences can be classified in a taxonomy with fairly limited branching. This taxonomy should be useful in evaluating various window managers, and it will also serve as a guide for the issues that need to be addressed by designers if future window-manager user interfaces. The advantages and disadvantages of the various options are presented. >

Valuator menu for use as a graphical user interface tool

Abstract: The system and method provides a user interface tool for simultaneously selecting a menu item and a value, from a range of values, for the menu item. The user interface tool is referred to as a valuator menu, since it allows both the selection of a value from a range of values, and the selection of a menu item from a menu list. As a user moves a cursor over a menu of selectable items on a screen display, the item underneath the cursor is highlighted. In addition, as the user moves the cursor within the highlighted menu item, a value relative to the position of the cursor within that menu item is displayed. This valuator value is dynamically updated as the cursor position changes within the menu item. When the user performs an input selection, i.e. through a mouse button or a keyboard interaction, both the selected menu item and the value, relative to the cursor position, are simultaneously returned to the application program running on the data processing system.

Learning by doing with simulated intelligent help

Abstract: Intelligent advisory interfaces will afford new approaches to help and training problems, however little is known about the usability of such facilities. This recent study indicates that although intelligent help can support users, there are also specific potential problems.

Hypertext and CASE

Abstract: Computer-aided software engineering (CASE) systems require a database system that must let designers logically associate documentation and source code, make annotations to record explanations and assumptions, and manage different versions of the software. The author reports the development of a database, Neptune, which demonstrates that hypertext provides an appropriate data model for CASE systems. Hypertext is a medium-grained, entity-relationship-like data model that lets information be structured arbitrarily and keeps a complete version history of both information and structure. Neptune achieves application independence by using a layered system architecture; at the bottom is a transaction-based server, the Hypertext Abstract Machine, and layered above it are applications and the user interface. The use of Neptune in the Dynamic Design CASE environment is discussed. >

A user interface toolkit based on graphical objects and constraints

Abstract: One of the most difficult aspects of creating graphical, direct manipulation user interfaces is managing the relationships between the graphical objects on the screen and the application data structures that they represent. Coral (Constraint-based Object-oriented Relations And Language) is a new user interface toolkit under development that uses efficiently-implemented constraints to support these relationships. Using Coral, user interface designers can construct interaction techniques such as menus and scroll bars. More importantly, Coral makes it easy to construct direct-manipulation user interfaces specialized to particular applications. Unlike previous constraint-based toolkits, Coral supports defining constraints in the abstract, and then applying them to different object instances. In addition, it provides iteration constructs where lists of items (such as those used in menus) can be constrained as a group. Coral has two interfaces: a declarative interface that provides a convenient way to specify the desired constraints, and a procedural interface that will allow a graphical user interface management system (UIMS) to automatically create Coral calls.

The designer as user: building requirements for design tools from design practice

Abstract: Software tools that support the design and development of interactive computing systems are an exciting possibility. The potential pay-off is great: user interface management systems, for example, promise not only to speed the process of specifying, implementing and maintaining user interface code, but also to guide the content of the user interfaces they support. As for any tool intended for human use, however, the success of software design tools will hinge on a thorough understanding of the problems they seek to address—design as it is practiced in the real world.