Myers, B. User-Interface Tools: Introduction and Survey. IEEE Software, Jan. 1989, pp. 15-23.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....2D applications, and have to deal with a design space for interaction tools and techniques that is larger and mostly unexplored. Moreover, as stated by Myers, the only reliable way to generate quality interfaces is to test prototypes with users and modify the design based on their comments [26]. User interface tools, such as toolkits or frameworks, have to be used in this iterative process to reduce development time. The lack of experience in 3D interfaces makes it particularly important for these tools not to enforce any particular interface style, but to provide a wide range of ....

Myers BA (1989), User-Interface Tools: Introduction and Survey. IEEE Software. 6(1): 15- 23.

....that are provided to the SVE runtime system to be invoked at certain phases of execution. Callback routines are commonly used for application specific extensions to a system. For example, event driven 2 D interface managers allow applications to respond to user interactions with the interface (Myers, 1989) by defining callback routines. In the next section, we describe how callback routines are used by VE applications using the SVE library. The library also allows the data associated with the environment model to be extended through named properties assigned to geometric objects. This mechanism is ....

Myers, B. A. (1989, January). User-interface tools: Introduction and survey. IEEE Software, pp. 15--23.

....Foley [12] Seeheim [13] or the reference model [14] and apply object orientation specifically to identify UI components and their relationships. However, the strictly layered structure of the underlying UI models imposes communication overheads that disqualifies them to support fast interactions [15]. Other proposals address the two needs design methodology and functional separation in a UI by providing the same separation of the layered UI models, presentation, dialogue control and semantic support, still organizing this layers in a nested structure. MVC [16] PAC [17] and the 4D model ....

B. A. Myers, "User-Interface Tools: Introduction and Survey," IEEE Software, pp. 15-23, January 1989.

....but it is also true for direct manipulation systems. Loose coupling is a desirable feature of any wellengineered software system and hence the user interface component of an application should, as far as possible, be separated from the application. This has led to the development of tools [Myers 89] which permit the user to define a user interface, as much as possible, in terms of the dialogue part in a manner largely independent of the application. 3.4.1 User Interface Toolkits User interface toolkits provide libraries of routines for creating and interacting with screen entities, ....

Myers, B.A.: 'User-Interface Tools: Introduction and Survey'. IEEE Software, pp 15 - 23, January 1989.

....space for 3D interaction tools and techniques remains mostly unexplored, while being far larger than in standard 2D applications. Moreover, as stated by Myers, the only reliable way to generate quality interfaces is to test prototypes with users and modify the design based on their comments (Myers 1989, p.15) The creation of complex interactive applications is an inherently iterative process that requires user interface tools, such as toolkits or frameworks. The lack of experience in 3D interfaces makes it extremely difficult to design 3D interface toolkits or frameworks. We believe that ....

Myers BA (1989) User-Interface Tools: Introduction and Survey. IEEE Software, Vol.6, No.1, pp.15-23.

....are poorly supported by common object models. Instead, we propose a model designed specifically to address the needs of graphics. Object orientation has much to offer graphics. It is widely acknowledged that graphics programming, especially interactive graphics programming, requires a lot of code [10]. Graphics problems are often complex, involving many special cases. Code to implement the interface of modern graphical applications is often half or more of the application s code. In addition, graphical applications are more common now than ever before. Since objectoriented programming is ....

Brad A. Myers. User-interface tools: Introduction and survey. IEEE Software, pages 15--23, January 1989.

....is a bottleneck restricting the potential of today s computational and communications technologies. When we begin to look for solutions to this problem, however, consensus evaporates. Myers states that the user interface typically accounts for 70 80 of the product cost of modern applications [120]. Beyond esthetics and user empowerment, this gives a bottom line incentive to software engineers to improve the efficiency and maintainability of interface models and technologies. 1.2.4 Why Adapt The recognition task is sufficiently onerous by itself. Why add the processing burden and ....

Myers, Brad. User-Interface Tools: Introduction and Survey. IEEE Software, Jan. 1989, 15-23.

....to create and maintain. This has been particularly troubling since good user interface design normally relies on an iterative approach based on experience and testing with real users. A fundamental goal behind much of the research in user interface management systems (UIMS) in the last decade [Pfaf85, Myer89] has been to make it much easier to produce interfaces so that iterative development is more economically feasible. One long term goal of this work has been to allow at least partial specification of interfaces by non programmers particularly by non programming experts in human factors, visual ....

Myers, B. A., "User Interface Tools: Introduction and Survey", IEEE Software, January 1989, pp. 15-23.

....space for 3D interaction tools and techniques remains mostly unexplored, while being far larger than in standard 2D applications. Moreover, as stated by Myers, the only reliable way to generate quality interfaces is to test prototypes with users and modify the design based on their comments (Myers, 1989). The creation of complex interactive applications is an inherently iterative process that requires user interface tools, such as toolkits or frameworks. 2 The lack of experience in 3D interfaces makes it extremely difficult to design 3D interface toolkits or frameworks. We believe that offering ....

Myers BA (1989) User-Interface Tools: Introduction and Survey. IEEE Software. 6(1): 15-23.

.... between the demands placed on the software industry (by a society that is t increasingly dependent on software, and increasingly intolerant of software failure) and what the state of the practice in he industry can deliver; also the brief history of the field abounds with instances of failure[19, 38, 67]. t t Software reuse offers a great deal of potential in terms of software productivity and software quality, because i ackles the above issues adequately: by dealing with software products at the component level, and by focusing on arbis trarily abstract descriptions of software components, it ....

....executf v able code. In addition to product artifact reuse, Horowitz considered various kinds of reuse based on the utilization o ery high level program producing systems [68] Three general classes of systems that have been commonly recognized c c by researchers are: 1) reusable program patterns [19, 68], whereby code or design patterns are used to instantiate specifi ode fragments or designs, as in application generators or the Programmer Apprentice s cliches [137] 2) reusable proces , w sors [68] which are interpreters for executable high level specifications, and 3) reusable ....

[Article contains additional citation context not shown here]

Brad A. Myers, "User-Interface Tools: Introduction and Survey," IEEE Software, pp. 15-23, January 1989. Spe1 cial issue on user interfaces

....including EPOS. This fact is amplified by the delicate balance between control and assistance , cf. the previous subsection. However, the problem of displaying complex and heterogeneous information to users with different levels of competence and goals, are shared by most computerised systems [Mye89] The general paradigm of user interfaces is that we should split how is works (internal model, e.g. in C or Prolog) from how to do it (external view) i.e. L3 or even L4. Some aspects to consider are: uniformity of presentation and interaction, easy comprehension of presented information, and ....

Brad A. Myers. User-Interface Tools: Introduction and Survey. IEEE Software, 6(1):15--23, January 1989.

....2D applications, and have to deal with a design space for interaction tools and techniques that is larger and mostly unexplored. Moreover, as stated by Myers, the only reliable way to generate quality interfaces is to test prototypes with users and modify the design based on their comments [26]. User interface tools, such as toolkits or frameworks, have to be used in this iterative process to reduce development time. The lack of experience in 3D interfaces makes it particularly important for these tools not to enforce any particular interface style, but to provide a wide range of ....

Myers BA (1989), User-Interface Tools: Introduction and Survey. IEEE Software. 6(1): 1523.

....Highly interactive systems based on a direct manipulation interaction style associated with multi thread dialogues are a good example of hardly tractable specification problems. 2 Different models and notations have been used to describe the interaction between an user and a computer [Mye89] State transition diagrams and one of their extensions, namely statecharts, shall be discussed next. The proposal of this paper is based on the Seeheim s logical user interface model depicted in Figure 1. The Seeheim model divides a user interface into three layers. The presentation layer is ....

....sophisticated, but it avoids some problems of the former. Both specification alternatives are graphical. This feature represents an advantage over textual descriptions employed by other specification languages. Further information about techniques employed to describe dialogues can be found in [Mye89] the transition network model class according to [Gre86] event model is used in textual languages like ALGAE [FB87] 3.1 State Transition Diagrams One way of representing an event driven control process is based on state transition diagrams. Specifically in the context of MS Windows ....

[Article contains additional citation context not shown here]

Brad A. Myers. User-Interface Tools: Introduction and Survey. IEEE Software, pages 15--23, January 1989.

....high level languages to describe the tasks of interest supported by those tools. Many techniques for interface control specification and implementation deal with the syntax of possible user actions, the reactions of interactive systems, and dialogue evolutions. Myers compares the most usual in [13], like state transition diagrams (STDs) These techniques, however, present several shortcomings. This paper analyses the problems of representing and implementing dialogue control components. An STD extension, namely the statechart notation, has been used for this purpose. Green presents three ....

....the statechart notation, has been used for this purpose. Green presents three interface models in [5] the transition net, the grammar and the event model. Although Green concludes that the event model has a greater expressiveness, each of those models has its own advantages and disadvantages [13]. The problems are in general due to a lack of mechanisms to represent particular features, usage difficulties and, in most cases, restrictions of representing a wide range of interface classes. Statecharts fit in the transition net model. Within the transition net notation class, statecharts ....

[Article contains additional citation context not shown here]

Brad A. Myers. User-Interface Tools: Introduction and Survey. IEEE Software, pages 15--23, January 1989.

....management system. Different phases of interface development (adapted from [10] The research area of user interface management systems has seen a lot of different systems and approaches. In [2] Foley et al. give an extensive literature survey which is not repeated here (see also Myers, [3]) In the following sections, I will focus on introducing some of the main UIMS trends, models and abstractions. Because interfaces usually contain graphical elements that can be directly manipulated, it seems to be apparent that the best way to construct them is to use interactive interfaces with ....

Myers, B.A., User Interface Tools: Introduction and Survey, IEEE Software, January 1989, pp. 15-23.

....be acquired by anonymous FTP as part of Garnet. For information on how to do this, contact garnet cs.cmu.edu. A complete reference manual for Lapidary is also available [30] Lapidary 5 2 Related Work Lapidary can be classified under the broad heading of User Interface Management Systems [24]. It provides capabilities that are found in interface builders, widget builders, application builders, behavior builders, and constraint builders. However, each of these types of tools allows only a limited set of graphics or behaviors to be specified. Lapidary goes beyond these tools in that it ....

Brad A. Myers. "User Interface Tools: Introduction and Survey". IEEE Software 6, 1 (Jan. 1989), 15-23.

No context found.

Myers, B. User-Interface Tools: Introduction and Survey. IEEE Software, Jan. 1989, pp. 15-23.

No context found.

B. Myers. User Interface Tools: Introduction and Survey. IEEE Software, 6(1):15--23, 1989.

No context found.

B. Myers, `User-interface tools: introduction and survey', IEEE Software, 15--23, January 1989.

No context found.

B. A. Myers, `User-interface tools: Introduction and survey'. IEEE Software, 15-23, Jan. 1989.

No context found.

B. Myers, User-interface tools: Introduction and survey. IEEE Software, Jan. 1989, pp. 15-23.

No context found.

Myers, Brad A. "User-Interface Tools: Introduction and Survey", IEEE Interface Systems, pp. 15-23, January, 1989.

No context found.

B.A. Myers. User-interface tools: introduction and survey. IEEE Software, January 1989, pp. 15--23,

No context found.

Brad A. Myers. User-Interface Tools: Introduction and Survey. IEEE Software, 6(1):15--23, January 1989.

No context found.

Brad A. Myers (1989), "User interface tools: Introduction and Survey", IEEE Software, vol. 6, no. 1, pp. 15-23. Jan.

First 50 documents

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC