Olsen, D. R., "A Programming Language Basis for User Interface Management," Human Factors in Computing Systems (CHI '89), (1989).  Home/Search   Document Not in Database   Summary   Related Articles   Check

....techniques [25] Here, the programmer provides a specification ( model ) of the properties of the application, along with specifications of the user and the display. This approach was moderately successful for creating dialog boxes [11, 27] and creating complete interfaces in a limited range [15, 25]. The ITS system from IBM was used to create all the screens for the information kiosks at the EXPO 92 worlds fair [29] Of particular note is the layout algorithm in the DON system that achieved a pleasing, compact, and logical placement of the controls [11] We extend these results to create ....

Olsen Jr., D.R. "A Programming Language Basis for User Interface Management," in Proceedings SIGCHI'89: Human Factors in Computing Systems. 1989. pp. 171-176.

....management systems (UIMSs) since they sought to execute user interfaces represented in a declarative way. The main aim of the MB UIDEs of this generation was to provide a proper way to execute a UI from the UIM. Examples of the the first generation of MB UIDEs are COUSIN [18] HUMANOID [44] MIKE [31], UIDE [24] and UofA [42] However, the UIMs of the first generation of MB UIDEs did not provide a high level of abstraction for the description of the UI. For instance, user interface aspects like layouts and widget customisation appeared early during the UI design process. Therefore, a new ....

D. Olsen. A Programming Language Basis for User Interface Management. In Proceedings of SIGCHI'89, pages 171--176, May 1989.

....These provide information about the current state of the user interface. Moreover, the generated user guidance component uses animation sequences to demonstrate how complex tasks can be accomplished by the user. 3 Related Work MIKE [18] Menu Interaction Kontroll Environment) und MIKEY [19] generate user interfaces with menus and dialog boxes based on a description of the functions (argument and result parameters) and the data structures in the application interface. In HIGGENS [10] a semantic data model of the application interface is used as the base for deriving views as ....

D. R. Olsen. A programming language basis for user interface managment. In ACM CHI 89 Proceedings. ACM, 1989.

....techniques [28] Here, the programmer provides a specification ( model ) of the properties of the application, along with specifications of the user and the display. This approach was moderately successful at creating dialog boxes [11] 29] and creating complete interfaces in a limited range [19][7] 28] The ITS system from IBM was used to create all the screens for the information kiosks at the EXPO 92 worlds fair [31] 32] Of particular note is the layout algorithm in the DON system that achieved a pleasing, compact, and logical placement of the controls [11] Other systems focused on ....

Olsen Jr., D.R. "A Programming Language Basis for User Interface Management," Human Factors in Computing Systems, Proceedings SIGCHI'89. Austin, TX, Apr, 1989, 1989. pp. 171-176.

....the email functional core: If the functional portion behaves asynchronously, then the UIMS is notified of the new arrival and holds the notification; If a synchronous scheme is used, then the functional core must memorize the fact until the user requires the delivery. Most of UIMSs such as Mickey [1], FormsVBT [2] UIDE [3] and MacIDA UIMS [4] support synchronous coordination only. In addition, most of them model the functional core as a semantic server: the UIMS has the initiative of the transfer of information (or, according to the classification of P. Tanner, dialog control is external ....

Olsen, D.R. Jr. A Programming Language Basis for User Interface Management. In Proceedings of the CHI'89 Conference (Austin, 30 April-4 May). ACM,1989, pp. 171-176.

....architecture of dialogue objects [4] A similar approach can be found in [7] Each dialogue object is responsible for one piece of the global conversation. The behaviour script of each dialogue object is formally specified by a rule language expressed in the first order predicate logic (see [16]) that can be partially depicted graphically by state transition diagrams [18] These diagrams allow an asynchronous representation of the task model in the conversation [12] The model based approach to the presentation will be discussed in this paper (Figure 6.1) Each process, denoted by a ....

D.R. Olsen, A Programming Language Basis for User Interface Management, in Proceedings of CHI'89, Austin, 30 April - 4 May 1989, pp. 171-176.

....architecture of dialogue objects [4] A similar approach can be found in [7] Each dialogue object is responsible for one piece of the global conversation. The behaviour script of each dialogue object is formally specified by a rule language expressed in the first order predicate logic (as in [16] that can be partially depicted graphically by state transition diagrams [18] These diagrams allow an asynchronous representation of the task model in the conversation [12] The model based approach to the presentation will be discussed in this paper (fig. 1) Each process, denoted by a ....

D.R. Olsen, A Programming Language Basis for User Interface Management, in Proceedings of CHI'89, Austin, 30 April - 4 May 1989, pp. 171-176.

....management systems (UIMSs) since they sought to execute user interfaces represented in a declarative way. The main aim of the MB UIDEs of this generation was to provide a proper way to execute a UI from the UIM. Examples of the the rst generation of MB UIDEs are COUSIN [18] HUMANOID [44] MIKE [31], UIDE [24] and UofA [42] However, the UIMs of the rst generation of MB UIDEs did not provide a high level of abstraction for the description of the UI. For instance, user interface aspects like layouts and widget customisation appeared early during the UI design process. Therefore, a new ....

D. Olsen. A Programming Language Basis for User Interface Management. In Proceedings of SIGCHI'89, pages 171-176, May 1989.

....( Menu= Customer Item= Search customer by id. will generate a Customer item on the menu bar associated with a menu item labelled Search customer by id. all other procedures associated with the same menu bar item will appear in the same pull down menu. In its Macintosh version, Mickey [8], the menus are generated in an equally straightforward manner. Fig. 1 Example of menu generated by MACIDA. MacIDA [11] automatically generates MacApp code for a Macintosh graphical UI from functional specifications contained in an information structure model (graphically depicted as an ....

D.R. Olsen. A Programming Language Basis for User Interface Management. In K. Bice, C. Lewis (eds.): Proc. of the ACM Conf. on Human Factors in Computing Systems CHI'89 (Austin, 30 April-4 May 1989). New York: ACM Press 1989, pp. 171176.

....Most of the tools that we discussed in the previous section take some representation of the application model, and generate an interface, without the designer having to specify the exact layout of the interface. In that sense, they can be classified as intelligent tools. UofA [74] and Mickey [75] generate presentation and dialogue from a specification of the application commands. GENIUS [76] takes a ER (Entity Relationship) data model to generate an interface that is consistent with the interface standards. It uses a knowledge base of several rules which describe the properties of a ....

....by the user. Automatic generation of interfaces comes at the expense of flexibility and range of designs that can be produced by these tools. ITS [72] and DON [80] focus on the creation of dialogue boxes for GUIs, but do not address other components needed for different dialogue styles. Mickey [75] automatically generates menu and dialogbox based UIs, Cousin [81] and Mecano [82] generate only form based UIs, while Diction [79] supports menu based UIs. However, some of the intelligent modelbased UIs discussed in the previous section, such as Humanoid and Tactics, provide several design ....

D.Olsen, "A Programming Language Basis for User Interface Management," Proc. CHI'89, (Austin, Texas, Apr.30-May 4, 1989), ACM, N.Y., 1989, pp.171-176.

....interface with a PIGUI toolkit, it will not provide a terminal independent user interface. Also, model based systems have not supported varying numbers of interfaces. Some model based UIMSs use editing to generate user interfaces from knowledge of data types of information in the application state [13, 14]. The data type declarations (maybe with additional formatting attributes) constitute the model. If a programming language supports introspection (i.e. it can analyze the type information of arbitrary objects at run time) then the model may not even be a separate entity. For example, Dost [5] ....

Dan R. Olsen, Jr. A programming language basis for user interface management. In Proceedings of CHI '89, pages 171--176, Austin, TX, April 30--May4, 1989.

....a task. After the users pushes Cancel Task the OMS is in its beginning state (users can select again the task they want to accomplish) 11.5 Related Work In HIGGENS [11] the semantic data model is used to derive views as abstract representations of user interface displays. MIKE [19] Mickey [20] and UofA [27] generate user interfaces out of a description of application actions and parameters. Compared to these systems, which had much influence on the development of BOSS, BOSS allows to exert more control over the different aspects of an interactive application s model, therefore ....

D. R. Olsen. A programming language basis for user interface managment. In ACM CHI 89 Proceedings. ACM, 1989.

....The display aspects of the interface were typically specified outside the specification language, in call back procedures that painted the screen as appropriate. Some UIMSs used as their main specification the type and procedure declarations that defined the functional aspects of the application [3, 29]. Based on this information, they generated menus to invoke the procedures, and dialogue boxes to prompt users for the information needed to construct instances of the types. Through the late 1980 s and early 90 s the specification languages became more sophisticated, supporting richer and more ....

Olsen, D.R.: A programming language basis for user interface managment. In Bice K., Lewis C. (eds.):.Proceedings of CHI'89. New York: ACM Press 1989 (pp. 171-176).

....lay out the widgets in a window. Automatic generation of dialog boxes from a high level textual specification description provides the possibility to automatically apply layout style rules to the design, avoiding some of the unnecessary steps described above. Jade [Zand90] ITS [Wiec90] and Mickey[Olse89] all generate dialog boxes from textual specifications. Mickey generates Macintosh user interface (menu s and dialog boxes) from interface descriptions embedded in Pascal. ITS and Jade use a set of style rules, created by a style expert and a specification of the dialog content to generate dialog ....

Olsen, D. A programming Language Basis for User Interface Management,CHI'89 Proceedings, Austin, Texas, may 1989, pp. 171-176.

No context found.

Olsen, D. R., "A Programming Language Basis for User Interface Management," Human Factors in Computing Systems (CHI '89), (1989).

No context found.

Olsen Jr., D.R. "A Programming Language Basis for User Interface Management," in Proceedings SIGCHI'89: Human Factors in Computing Systems. 1989. pp. 171-176.

No context found.

D. Olsen. A Programming Language Basis for User Interface Management. In Proceedings SIGCHI'89. April

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