NeXT, Inc. 1990. Interface Builder, Palo Alto, CA.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....of states that occur in state transition networks. In fact, command and input group sequencing attributes can be used to emulate all the dialogue structures supported in the UofA UIMS [18] plus provides the framework to define others. Interface builders such as the Next Interface Builder [13], and OpenInterface [12] are a different class of tools to aid in the design of interfaces. These tools allow designers to draw interfaces consisting of check boxes, radio buttons, labels, type in areas and other such interface building blocks. These tools make it very easy to construct the ....

NeXT, Inc. 1990. Interface Builder, Palo Alto, CA.

....easily specify the dialogue structures that MIKE and 6 UofA support. We also provide finer control over presentation design, and offer richer descriptions of application semantics that can be used to support more sophisticated design tools. Interface builders such as the Next Interface Builder [14], and OpenInterface [13] are a different class of tools to aid in the design of interfaces. These tools make it very easy to construct the particular interfaces that they support, but are very poor for design exploration. Designers have to commit to particular presentation, layout and interaction ....

NeXT, Inc. 1990. Interface Builder, Palo Alto, CA.

....that facilitate low level design and implementation and that support paradigms of intertwined design and implementation [6, 33] do not provide an adequate balance between providing high level design automation and giving designers extensive control over interface design. Interface builders (e.g. [24, 25]) and automatic interface generation systems (e.g. 2, 10, 13, 26, 30] represent tools of this kind. Interface builders offer designers extensive control over certain tasks (such as defining the properties of a push button: shading, color, label, font, size, and so on) with an iterative ....

NeXT, Inc. 1990. Interface Builder, Palo Alto, CA.

....Representation. INTRODUCTION Today s interface design tools do not strike an adequate balance between giving designers control over an interface design, and providing a high level of design automation. Tools that give designers extensive control over details of a design, like interface builders [14], typically force designers to control all details of the design. Tools that automate significant portions of interface design, like MIKE [15] and UofA [16] typically let designers control few of the details. This paper describes our efforts to combine the benefits of these two classes of tools ....

....key problem is to help designers search the design space quickly and effectively. It is interesting to consider how interface builders and automated generation systems, the two main current approaches, fare when judged in terms of support for exploration of design alternatives. Interface builders [13, 14] allow designers to draw the screens of an application. They are most effective for concrete tasks such as constructing the static portion of interfaces and editing screen layouts. But, working at this level, they force designers to handle far too much detail. To use the tools, designers are ....

[Article contains additional citation context not shown here]

NeXT, Inc. 1990. Interface Builder, Palo Alto, CA.

No context found.

NeXT90 NeXT, Inc. 1990. Interface Builder, Palo Alto, CA.

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