In web-based applications, the dialog control logic is often hidden in or entwined with the presentation and/or application logic, even if the latter tiers are well-separated. This makes it difficult to control complex dialog structures like nested dialogs, and to reconcile the device-independent business logic with the device-specific interaction patterns required by different clients ’ I/O capabilities. To avoid continuous re-implementation of the dialog control logic, we present a Dialog Control Framework that is separate from the presentation and business tiers, and manages arbitrarily nested dialog flows on different presentation channels. The framework relies on dialog specifications developed using the Dialog Flow Notation, which are translated into an object-oriented dialog flow model for efficient run-time lookups. This way, the framework automates the dialog control aspect of web-based application development and leaves only the tasks of implementing the business logic, designing the hypertext pages, and specifying the dialog flow to the developer. 1.

Abstract not found

This report gives a survey of user interface languages and formal representations of user interfaces. The following aspects of User Interface Languages are considered: ffl expressiveness ffl readability ffl evaluation (is it possible to evaluate the ergonomic and functional quality of the user interface from the representation) ffl manipulation ffl compilation/interpretation ffl possibility to include knowledge representation.

Model Restructured Abstract Model Detection Transformation Generation (Forward Engineering) (Reverse Engineering) Representation Representation Human Analyst Input 2 Several good surveys of representations for designing user interfaces exist [ABO89],[DIX93], [FOL90], [HAR89], [GRE87]. Almost all existing representations were developed for one or more development-oriented purposes: . Designing a new system (communication with implementers) . Analyzing usability or performance of an existing system (communication with interface designers) . Documenting an existing or developmental system (communication with end users) While these representations were developed to give the designer or analyst a framework for developing or improving an interface, they were not intended to support the recovery of a system-level interface specification from a legacy application. Design notations were developed to describe a "perfect world" - to organize the creation of a new system. They were not intended ...

specification

Domain-independent, high-level, flexible, and efficient user interface development environments (UIDEs) are required for easing the task of developing multi-user interfaces. This paper describes several principles of designing such environments, gives motivation for supporting them, and identifies existing systems that follow them. Some of these principles are also well-accepted principles of designing single-user UIDEs---multi-user interaction provides new reasons for accepting them. Others are single-user principles that have been adapted for the multi-user case, while still others are new principles that have no counterparts in the single-user case. These principles address the functionality and architecture of a multi-user UIDE and the programs supported by it. Keyword Codes: C.2.4; D.2.2; H.1.2 Keywords: Distributed Systems; Tools and Techniques; User/Machine Systems 1. INTRODUCTION Most of the current principles of designing user interface development environments (UIDEs) [5, 15...

We present a game-based architecture for developing complex interactive components in computational logic. Interactive components are developed either as players making moves according to the rules of a game or as umpires that enforce the rules, thereby controlling the behaviours of players. Centralised organisations based on umpires and decentralised organisations based on autonomous players can then be combined to produce interactive systems of a very complex nature. The potential

The ideas and findings in this report should not be construed as an official DoD position. It is published in the interest of scientific and technical information exchange. FOR THE COMMANDER (signature on file)

Personalization constitutes the mechanisms necessary to automatically customize information content, structure, and presentation to the end-user to reduce information overload. Unlike traditional approaches to personalization, the central theme of our approach is to model a website as a program and conduct website transformation for personalization by program transformation (e.g., partial evaluation, program slicing). The goal of this paper is study personalization through a program transformation lens, and develop a formal model, based on program transformations, for personalized interaction with hierarchical hypermedia. The specific research issues addressed involve identifying and developing program representations and transformations suitable for classes of hierarchical hypermedia, and providing supplemental interactions for improving the personalized experience. The primary form of personalization discussed is out-of-turn interaction – a technique which empowers a user navigating a hierarchical website to postpone clicking on any of the hyperlinks presented on the current page and, instead, communicate the

Abstract not found