Pedro A. Szekely and Brad A. Myers. "A User Interface Toolkit Based on Graphical Objects and Constraints". Sigplan Notices 23, 11 (Nov. 1988), 36-45. ACM Conference on Object-Oriented Programming; Systems Languages and Applications; OOPSLA'88.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....Display object has a collection of objects also organised in accordance with the four elements of the model. This composition originates a recursive model [18] Data Application abstract information This component provides common usage data structures (int, file, list, with active values [19], i.e. values that automatically propagate their changes. Some Data objects also represent semantic actions of the application. The primary reason for the existence of Data objects is to provide a clear interface between UI and computational parts while including semantic information on the UI ....

P. A. Szekely and B. A. Myers, "A User Interface Toolkit Based on Graphical Objects and Constraints, " in OOPSLA'88 Conf. Proc., pp. 36-45, San Diego, September 1988.

....similar approaches have been taken elsewhere. For example, in InterViews, pane layout is described by means of horizontal and vertical boxes, which may serve as glue between interaction objects [10] Other toolkits use constraints for describing the geometrical dependencies for a layout [1, 20]. Encapsulating the layout information in a layouter, as in Xit, has several advantages. The layout description is independent of the objects to be arranged. Parts may be added or removed without changing the description. Furthermore, the layout can be easily modified or switched by simply ....

....in the application. Also, class specific update methods have to be defined, which cannot be specialized for particular instances. Various systems employ active values or constraints for linking user interface and application establishing dependencies between interface and application attributes [2, 4, 20]. In contrast to this, the read write mechanism of Xit, which is solely described on the part of the user interface, ensures a clear separation from the application and is smoothly integrated with the eventbased reactivity specification. Since actions for read and write events can contain ....

P. A. Szekely and B. A. Myers. A User Interface Toolkit Based on Graphical Objects and Constraints. In OOPSLA'88 Proceedings, pages 36--45. ACM, 1988.

....simultaneously be executed on a range of different devices in order to present displays to a number of different users. If one instruction were omitted or placed out of sequence then the final image might be corrupted. Szekely and Myers identify a further limitation of procedural graphics systems [24]. If users select part of a display, using a mouse or some cursor keys, then there is no means of identifying the target of their selection using the instructions that generated the image. Designers must, therefore, maintain additional data structures in order to determine which images are ....

P. Szekely and B. Myers. A user interface toolkit based on graphical objects and constraints. ACM SIGPLAN Notices, 23(11):36--45, 1988.

.... extension of visual object oriented programming thoroughly discussed in [1] The extension lies in different encapsulation of objects and different usage of classes which is inherent to the NUT system [2] With this respect, our technique is similar to visual programming based on constraint nets [3] or data flow [4] The novelty of the present work is, first of all, in a uniform representation of semantics of visual images and schemes composed from the images. We use images instead of icons for representing objects. An image includes, as a rule, a number of elements with their own meaning: ....

P. Szekely & B. Myers (1988) A user-interface toolkit based on graphical objects and constraints. In: Proceedings of the 1988 ACM Conference on Object-Oriented Systems, Languages and Applications, San Diego, pp. 36-45.

....the relationship that the right side of a rectangle should be located width pixels from the left side of the rectangle. Constraints find use in a great many applications, including spreadsheets, graphical interface toolkits [Myers et al. 1990; Barth 1986; Henry and Hudson 1988; Hudson 1994; Szekely and Myers 1988; Vander Zanden 1988; Myers 1990; Hill et al. 1994] graphical layout systems [Gosling 1983] simulation systems [Borning 1981; Borning and Duisberg 1986] animations [Duisberg 1986] programming languages [Freeman Benson 1990; Maloney 1991; Hoover 1992] and programming environments [Reps et al. ....

Szekely, P. A. and Myers, B. A. 1988. A user interface toolkit based on graphical objects and constraints. Sigplan Notices 23, 11 (Nov.), 36--45. ACM Conference on Object-Oriented Programming; Systems Languages and Applications; OOPSLA'88.

....for electrical circuits using local propagation. CONSTRAINT [VanderZanden88] is a language with which graphical objects and subobjects may be displayed and modified, while satisfying a set of constraint equations, ordering these equations for optimal update to ensure real time interaction. Coral [Szekely88] is a declarative language for declaring aggregate objects and expressing unidirectional constraints between those objects. Part of the Garnet system is a unidirectional constraint language called KR built on Common Lisp. Bertrand [Leler88] on which Siri is partially based, is a general purpose ....

Szekely, P., and Myers, B.A. A User Interface Toolkit Based on Graphical Objects and Constraints. OOPSLA/Sigplan Notices 23(11): 36:45, November 1988.

....constraints between their successive states, so that in the absence of stronger constraints, a variable will retain its value over time. There has also been much applications oriented work on using constraints, for domains such as geometric layout [3, 29, 49, 74, 78] user interface toolkits [2, 46, 47, 48, 75], electrical circuit analysis [70, 73] and even jazz composition [40] Regarding constraint hierarchies, our original description of constraint hierarchies is in reference [4] DeltaBlue, an efficient, incremental algorithm for finding a locally predicate better solution to a constraint hierarchy ....

Pedro Szekely and Brad Myers. A User-Interface Toolkit Based on Graphical Objects and Constraints. In Proceedings of the 1988 ACM Conference on Object-Oriented Programming Systems, Languages and Applications, pages 36--45, San Diego, September 1988. ACM.

....of nodes may depend on adjoining nodes or the topology of edges (e.g. in order to avoid line crossing or long winding paths) This problem is addressed by many constraint oriented systems. ThingLab I [3] and II [14] are examples for describing layout of graphical objects with constraints. [16] also presented a toolkit using constraints and active values. In contrast to constraint oriented approaches we decided to provide a simpler but more compact and predictable notation for specifying layout. Furthermore, our approach has the advantage that it requires only 2n log(n) steps, be n ....

P.A. Szekely, B.A. Myers, A User Interface Toolkit Based on Graphical Objects and Constraints, ACM Sigplan Notices 24, 10 (1989), 36--45.

....using integer data. For example, bar charts can be realized using rectangles whose sizes are proportional to integer data fields. Second, we need a better communication method between computation modules and the GUI modules that IMAGE generates. We are currently planning to adopt active values[13] in the short term, but a better approach is needed for complex interactions. Finally, the drawing editor can be improved to give more interactive feedback to programmers in the rule generation process. For example, when a programmer moves a rectangle, the editor could snap the rectangle onto a ....

Szekely, P. A. and G. A. Myers, "A User Interface Toolkit Based on Graphical Objects and Constraints, " in Proc. of ACM Object-Oriented Programming Systems, Languages, and Applications, 1988, pp. 36--45.

.... Magritte [20] the celebrated Sketchpad system [44] and ThingLab I [2] Constraints have been used in a fair number of user interfaces and user interface construction systems, including Animus [10] the Cactus statistics exploration environment [33] the Constraint Window System (CWS) 12] Coral [45], Fabrik [26] the FilterBrowser user interface construction tool [11] Garnet [35] GITS [37] GROW [1] Peridot [34] Picasso [38] RENDEZVOUS [21, 22] the RTL CRTL tiled window layout system [7] and ThingLab II [31, 32] Finally, researchers have developed several general purpose languages ....

Pedro Szekely and Brad Myers. A User-Interface Toolkit Based on Graphical Objects and Constraints. In Proceedings of the 1988 ACM Conference on Object-Oriented Programming Systems, Languages and Applications, pages 36--45, San Diego, September 1988. ACM.

....of nodes may depend on adjoining nodes or the topology of edges (e.g. in order to avoid line crossing or long winding paths) This problem is addressed by many constraint oriented systems. ThingLab I [4] and II [22] are examples for describing layout of graphical objects with constraints. [27] also presented a toolkit using constraints (let ( left table (make dialog item . right table (make dialog item . graph view (make layout view . make layout dialog :layout ( vbox ( width :filler :height :filler) hbox ( height 1 4 :width :filler) fbox ( left table) fbox ....

P.A. Szekely, B.A. Myers, A User Interface Toolkit Based on Graphical Objects and Constraints, ACM Sigplan Notices 24, 10 (1989), 36--45.

....interfaces, both as an aid in interface development and as an interaction paradigm. Constraints can specify spatial and semantic relationships declaratively between objects in a user interface, while an underlying constraint solver will ensure that interface meets the specification. Previous work [2, 3, 5, 16, 20, 13, 21, 22] has established that constraint systems need at least the following capabilities to be effective in graphical user interfaces: An earlier version of this paper appears in Proceedings of the Third Eurographics Workshop on ObjectOriented Graphics, Champ ery, Switzerland, October 1992. To appear ....

P.A. Szekely and B.A. Myers. A user interface toolkit based on graphical objects and constraints. In Object-Oriented Programming Systems, Languages and Applications Conference, pages 36--45, 1988.

....constraint systems. Sketchpad is the first GUI system that adopts a local propagation technique called one pass method (it also uses numerical methods on failure of the one pass method) 79] Most systems employ one way constraints, whose output variables are predetermined by programmers [42, 63, 64, 65, 66, 81]. By contrast, Fabrik handles two way constraints, each of which has two potential output [47] and ThingLab [3, 6] and CONSTRAINTS [78] exploit multi way constraints, where each variable can be an output. In the context of local propagation for ordinary systems, researchers have been investigated ....

Szekely, P. A. and G. A. Myers, "A User Interface Toolkit Based on Graphical Objects and Constraints," in Proceedings of the ACM Conference on Object-Oriented Programming Systems, Languages, and Applications (OOPSLA), Sept. 1988, pp. 36--45.

.... should respond to input events, and 5) hierarchically compose complex objects from simpler objects [39, 47, 49, 35, 20, 2, 4, 22, 37] Because of their utility, dataflow constraints are now used in a wide variety of interactive applications, including spreadsheets, graphical interface toolkits [35, 2, 20, 27, 46, 47, 36, 34, 22], graphical layout systems [18] simulation systems [3, 4] animations [12] imperative programming languages [14, 33] and programming environments [37] QuickPlan 4 3 Why Multi Output, Multi Way Dataflow Constraints are Important One way constraints handle many aspects of interactive ....

Pedro A. Szekely and Brad A. Myers. "A User Interface Toolkit Based on Graphical Objects and Constraints". Sigplan Notices 23, 11 (Nov. 1988), 36-45. ACM Conference on Object-Oriented Programming; Systems Languages and Applications; OOPSLA'88.

No context found.

Pedro A. Szekely and Brad A. Myers. "A User Interface Toolkit Based on Graphical Objects and Constraints". Sigplan Notices 23, 11 (Nov. 1988), 36-45. ACM Conference on Object-Oriented Programming; Systems Languages and Applications; OOPSLA'88.

No context found.

P. Szekely and B. Myers. A user-interface toolkit based on graphical objects and constraints. In Proceedings of the 1988 ACM Conference on Object-Oriented Programming Systems, Languages and Applications, pages 36--45, September 1988.

No context found.

Szekely, P. and Myers, B. A User Interface Toolkit Based on Graphical Objects and Constraints. Proceedings OOPSLA '88, ACM SIGPlan Notices 23,11 (1988), pp. 36-45.

No context found.

P. Szekely and B. Myers. A user interface toolkit based on graphical objects and constraints. Journal of A.C.M. SIGPLAN Notices, 23#11#:36#45, November 1988.

No context found.

Pedro Szekely and Brad Myers, `A user-interface toolkit based on graphical objects and constraints', Proc. 1988 ACM Conference on Object-Oriented Programming Systems, Languages and Applications, ACM, San Diego, September 1988, pp. 36--45.

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