Dewan, P. "A tour of the suite user interface software," Proceedings of 3rd ACM SIGGRAPH Symposium on User Interface Software and Technology, pages 57--65, Oct 1990.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....to focus on the provision of facilities to support the sharing of multi user interfaces across a user community. The use of different views of shared elements has emerged as a definite theme within CSCW interfaces. Private or personal views are supported in a number of recent systems such as Suite[2], Liza [7] and CES [15] A number of architectures also exist, 14, 1] which support these views through the use of an underlying object model. The model maintains a clear logical separation between a shared object and its views, and separate individual user interfaces are derived from the ....

....within access models to manage the tailoring and modification of graphical user interfaces in groupware applications provides us with a well understood mechanism for tailoring the cooperating user interfaces. Access models are used in only a few collaborative systems, such as RTCAL [8] Suite [2] and Grove [4] In fact, Shen [16] highlights the need for access control in collaborative systems in general and argues that most collaborative systems give all collaborators the same rights to all objects and expect access to be controlled by some social protocol . The lack of a generally ....

Dewan P., "A tour of the Suite User Interface Software." Proc. of the 3rd ACM SIGGRAPH Symposium on User Interface Software and Technology, October 1990, pp 57-65.

....system, for example, Garnet [28] and Rendezvous [23] This will maintain status status mappings on behalf of the developer, although one should be aware that they do not guarantee immunity from the problems of mediated mappings as was demonstrated above. Active variables as used in Suite [9, 10] are also a way of supporting status status mappings by automatically generating appropriate change events. Furthermore, Suite supports shared variables over distributed platforms. Of course, it does not absolve the designer from considering the issues of mixed control of shared variables ....

P. Dewan. A tour of the Suite user interface software. In UIST'90: Proceedings of the 3rd ACMSIGGRAPH Symposium on User Interface Software and Technology, pages 57--65. ACM, 1990.

....aspects of the system; Depending on the software development environment, the designer may be concerned with additional issues such as allocating structural components to processes and allocating processes to physical processors. Groupware development tools such as Groupkit [22] and Suite [9], tend to alleviate the problem of process and processor allocation. While the application of principled design is widely recognised in the software community, there is very little material to help architectural designers to cope with a number of major difficulties. These include finding the ....

Dewan, P. A tour of the Suite User Interface Software, in Proceedings UIST'90, ACM, 1990, 5765

....switched into a synchronous mode of participation. CONCLUDING REMARKS In recent years, several conferencing systems have been proposed and prototyped to improve the effectiveness of personto person collaborations. Lantz [5] have studied conferencing architectures for text and graphics. Dewan [4] has addressed the issue of sharing and coupling among windows displaying shared workspace. Ahuja et al. at AT T Bell Laboratories [2] and Aguilar et al. at SRI [1] propose architectures for person to person audio and or video conferencing. Connection management architectures for providing flexible ....

P. Dewan. A Tour of the Suite User Interface Software. In Proceedings of the 3rd ACM SIG-GRAPH Symposium on User Interface Software and Technology, pages 57--65, October 1990.

....views of the electrician and hydraulics engineer. Implementing Re Coupling in non 3D environments User interface re coupling can be used to enhance shared user interfaces, other than those of 3D virtual environments. Many shared 2D user interface systems, such as SOL [17] Suite [3] and GroupKit [16] support individual user interface tailoring and a range of user interface coupling means. The notion of awareness based re coupling can be introduced into these systems to both promote a common understanding throughout the potentially different interfaces, and aid in the ....

Dewan P. (1990). "A tour of the Suite User Interface Software". Proc. of the 3rd ACM SIGGRAPH Symposium on User Interface Software and Technology. October 1990. 57-65.

....management and control of different users world views. Users and developers should be provided with the flexibility to quickly amend their views of the world to effectively support the cooperative nature of the tasks taking place. Many 2D based multi user interface systems exist, including Suite [7], SOL [18] Mead [3] Rendezvous [15] and GroupKit [16] All of which support tailorable user interfaces across a community of users who may have different preferences. The model offered by these systems allows the shared data to be viewed in different ways by a number of users. However, there is ....

Dewan P. (1990). A tour of the Suite User Interface Software. Proc. of the 3rd ACM SIGGRAPH Symposium on User Interface Software and Technology. October 1990. 57-65.

....system. This approach and its associated problems are discussed in Section 6.3. The CSCW field has conducted research into the requirements of groupware, and has produced toolkits to aid in the construction of groupware systems. Three notable examples are GroupKit [16] Rendezvous [12] and Suite [5]. These toolkits are relevant to the TI technique in the way in which they integrate user interface and groupware services. There are several major differences. First, these systems do not use a separate service to provide groupware features; instead, the toolkit is the groupware system. Second, ....

P. Dewan. A tour of the Suite user interface software. In Proceedings of the Third Annual Symposium on User Interface Software and Technology, pages 57--65, Snowbird, UT, October 1990. Association for Computing Machinery.

....Data Image Data Audio Video Data O R a i d D a t a b a s e Layer 1 Layer Layer Layer Layer 2 3 4 5 Figure 1: The architecture for a multimedia system understand the complex structure of the multimedia database. We have prototyped a graphical interface called O UI [12] using the Suite system [2] for the O RAID database system at Purdue University. Suite provides a dialogue manager to manage the user interface aspects of the application. The Suite dialogue manager will be used to interactively refine the user query. Several options and display modes will be presented to the user which ....

Prasun Dewan, A Tour of the Suite User Interface Software, In Proceedings of the a3rd ACM SIGGRAPH Symposium on User Interface Software and Technology, pp57-65, Oct. 1990.

....inheritance from application objects. This is similar in concept to the way Chiron artists are built, since they obtain much of their interface from the package specifications of the object they display. Chiron, in its Ada implementation, cannot use inheritance for this purpose. The Suite system [2] implements a distributed architecture that supports groupware. The distributed architecture of Suite is similar to Chiron s client server orientation, but is more fully exploited in Suite. In Suite, however, editing is the main metaphor for user interaction and graphics are not supported. The ....

P. Dewan. A tour of the suite user interface software. In Proceedings of the Third Annual Symposium on User Interface Software and Technology, pages 57--65, Snowbird, UT, October 1990. Association for Computing Machinery.

.... DistEdit [57] a domain specific tool for constructing shared editors based on the ISIS [4] framework; and SUITE [18] 20] a system that provides support for several dimensions of coupling between replicated data structures and views, based on the SUITE user interface management system [21][22]. Very few collaboration support environments, however, have addressed the information sharing problems that must be overcome to satisfy the coordination requirements of collaborative applications, which often 20 derive from social issues. Recall that coordination requirements in collaboration ....

Dewan, Prasun. "A Tour of the Suite User Interface Software," Proceedings of the 3rd ACM SIGGRAPH Symposium on User Interface Software and Technology, October 1990, pp. 57-65.

....Application Access Control Interaction Policy User Figure 3: The use of a common interface definition The use of different views of shared elements has emerged as a definite theme within real time cooperative interfaces. Private or personal views are supported in a number of systems such as Suite [14], Liza [15] and CES [16] A number of architectures also exist [11, 12] which support these views through the use of an underlying object model. The model maintains a clear logical separation between a shared object and its views, and separate individual views are derived from the underlying ....

....Many other models are further derived from these two. Current access models were not designed for collaborative information, and are inappropriate for direct inclusion in collaborative systems[19] Simple access models are used in only a few collaborative systems, such as RTCAL [18] Suite [14] and Grove [8] In fact, Shen [19] highlights the need for access control in collaborative systems in general and argues that most collaborative systems give all collaborators the same rights to all objects and expect access to be controlled by some social protocol . We have therefore developed ....

Dewan P., "A tour of the Suite User Interface Software." Proc. of the 3rd ACM SIGGRAPH Symposium on User Interface Software and Technology, October 1990, pp 57-65.

....wakes up tense because the sounds of the jungle have ceased. In computational system s we get a similar effect when there is some sort of gatekeeper , a primitive agent which can inform other agents of status changes (but have no independent initiative) Examples of this include active values [10] and some databases with triggers. S A gatekeeper of status tells target agent . SA target agent watches source status 4.5 Trigger Finally, we need to know what event triggered the interaction. In the case when the status is the source and initiative (S S and S A) then this can only be the ....

....in the X Motif callbacks [34] and in the Java JDK 1.1 source listener event model [25] A similar mechanism is the use of active values, variables which invoke callbacks when modified. These were first used in the InterLisp environment within a single machine, but have also been adapted in Suite [10, 11] as the main mechanism for a distributed multi user interface development toolkit. A more sophisticated option is when the toolkit embodies a constraint maintenance system as in the case of Garnet [33] for single user interfaces and Rendezvous [28, 29] for distributed, multi user interfaces. In ....

Dewan, P. A tour of the Suite user interface software. in UIST'90: Proceedings of the 3rd ACM SIGGRAPH Symposium on User Interface Software and Technology. 1990. ACM Press. p. 57--65.

....of A T ; menu add starts with default values of the components; menu show does not allow modification of the variable. Customizing of the display is impossible. The implementation of this tool is not available. 7.3 Display generation systems 7.3. 1 Dost and Suite systems The group of systems [Suite91, Dewan91A, Dewan91] designed by Parsun Dewan can display data structures to one or more users and responds to user modifications to these data structures. DOST [Dewan90, Dewan87] is an early prototype of SUITE. In a C program some data types should be defined. Then the variables of these types can be passed to the ....

P. Dewan. A Tour of the Suite User Interface Software. Included in

....mappings require event mediation. In languages that do not have events, such as constraint systems, this mediation is hidden from the designer and can result in undesirable delays or unanticipated inconsistencies. A second implementation mechanism, used for example in the Suite system [6, 7], is the active variable. Active variables automatically generate appropriate change events in order to sustain status status mappings. But Suite implements a particular policy for dealing with the issue of mixed control and the designer must decide whether these policies are appropriate or alter ....

Dewan, P. A tour of the Suite user interface software. In UIST'90: Proceedings of the ACM Symposium on User Interface Software and Technology (1990), ACM, pp. 57--65.

....Lantz [16] proposes a text graphics teleconferencing architecture whose goal is to fit into existing systems with minimal impact, and Sarin and Greif [26] have studied teleconferencing architectures for text and graphics, but have not explored time dependent media such as audio and video. Dewan [10] has addressed the issue of sharing and coupling among windows A Formal Basis for Structured Multimedia Collaborations 2 displaying shared workspaces. Casner et al. at ISI [6] have developed media transport protocols for teleconferencing among geographically distributed sites in wide area packet ....

P. Dewan. A tour of the suite user interface software. In Proceedings of the 3rd ACM SIG-GRAPH Symposium on User Interface Software and Technology, pages 57--65, October 1990.

....from application objects. This is similar in concept to the way Chiron artists are built, since they obtain much of their interface from the package specifications of the object they display. Chiron, in its Ada implementation, cannot use inheritance for this purpose, however. The Suite system [Dew90] implements a distributed architecture that supports a groupware service . The distributed architecture of Suite is similar to Chiron s client server orientation, but is more fully exploited in Suite. In Suite, however, editing is the main metaphor for user interaction and graphics are not ....

Prasun Dewan. A tour of the suite user interface software. In Proceedings of the Third Annual Symposium on User Interface Software and Technology, pages 57--65, Snowbird, UT, October 1990. Association for Computing Machinery.

....sharing of multi user interfaces across a user community. Smith, Rodden An access model for shared interfaces 4 The use of different views of shared elements has emerged as a definite theme within CSCW interfaces. Private or personal views are supported in a number of recent systems such as Suite[2], Liza [7] and CES [15] A number of architectures also exist, 14, 1] which support these views through the use of an underlying object model. The model maintains a clear logical separation between a shared object and its views, and separate individual user interfaces are derived from the ....

....within access models to manage the tailoring and modification of graphical user interfaces in groupware applications provides us with a well understood mechanism for tailoring the cooperating user interfaces. Access models are used in only a few collaborative systems, such as RTCAL [8] Suite [2] and Grove [4] In fact, Shen [16] highlights the need for access control in collaborative systems in general and argues that most collaborative systems give all collaborators the same rights to all objects and expect access to be controlled by some social protocol . The lack of a generally ....

Dewan P., "A tour of the Suite User Interface Software." Proc. of the 3rd ACM SIGGRAPH Symposium on User Interface Software and Technology, October 1990, pp 57-65.

....and so, changing aspects of one display will have minimal impact on other Displays (although a single Display might be included in more than one user s working set ) 2.4. 4 Suite Suite is multi user application toolkit derived from an earlier, single user application toolkit of the same name (Dewan, 1990; Dewan and Choudhary, 1992) Suite focuses on editor based interfaces implemented over a shared data model. Sharing and coordination in Suite is achieved through the linkage between shared active variables and interaction variables. Essentially, this is the point where multi user fan out takes ....

Dewan, P. (1990). "A Tour of the Suite User Interface Software", in Proc. ACM Conference on User Interface Software and Technology UIST'90 (Snowbird, Utah).

....to focus on the provision of facilities to support the sharing of multi user interfaces across a user community. The use of different views of shared elements has emerged as a definite theme within CSCW interfaces. Private or personal views are supported in a number of recent systems such as Suite [2], Liza [7] and CES [15] A number of architectures also exist, 14, 1] which support these views through the use of an underlying object model. The model maintains a clear logical separation between a shared object and its views, and separate individual user interfaces are derived from the ....

....the interface as being derived from a set of shared objects we choose to view the problem as one of a shared interface constructed from a collection of interface objects and access to this shared interface. Simple access models are used in only a few collaborative systems, such as RTCAL [8] Suite [2] and Grove [4] In fact, Shen [16] highlights the need for access control in collaborative systems in general and argues that most collaborative systems give all collaborators the same rights to all objects and expect access to be controlled by some social protocol . However, more generally, ....

Dewan P., "A tour of the Suite User Interface Software." Proc. of the 3rd ACM SIGGRAPH Symposium on User Interface Software and Technology, October 1990, pp 57-65.

No context found.

Prasun Dewan, `A tour of the Suite user interface software', Proceedings of the 3rd ACM SIGGRAPH Symposium on User Interface Software and Technology, October 1990, pp. 57--65.

....also includes a new, efficient multiuser architecture, which centralizes semantic information but replicates the syntactic information. The infrastructure has been successfully implemented in a software system called multiuser Suite, which is an extension of single user Suite. Single user Suite [3] is a User Interface Development Environment (UIDE) that resulted from our research on single user user interfaces. It includes a distributed persistent object system [4] and a mechanism for associating inheritable attributes with active variables [5] Our approach to extending single user Suite ....

Prasun Dewan, "A Tour of the Suite User Interface Software," Proceedings of the 3rd ACM SIGGRAPH Symposium on User Interface Software and Technology, October 1990, pp. 57-65.

....building and using objects in Suite, and presents conclusions and future directions for research. ################################################################################################ 1. INTRODUCTION Our interest in objects [25] stems from our work on the Suite user interface software [11]. Two of the goals of Suite are to support (i) loosely coupled interactive applications, that is, applications whose interactive and computational components execute in different address spaces residing possibly on different hosts, and (ii) collaborative applications, that is, applications that ....

....representation of the current list of appointments (Figure 5) The user interface of an object is implemented by a generic language independent dialogue manager, which is itself an object defined by a system provided class, as discussed later. More details on the user interface can be found in [11]. Other interactive object based systems such as Eden [1] and Hydra [22] offer command languages for interactively sending messages to objects. Command oriented object manipulation complements editor oriented object maniuplation since it allows users to manipulate objects that are not displayed in ....

Prasun Dewan, A Tour of the Suite User Interface Software, Proceedings of the 3rd ACM SIGGRAPH Symposium on User Interface Software and Technology, pp. 57-65 (October 1990).

....which are associated with values that have been changed, checked for syntax errors, checked for semantic errors, and committed, respectively. In Suite, a committed value is guaranteed to be free of semantic errors and a value free of semantic errors is guaranteed to be free of syntax errors [9]. Suite defines two attributes, called feedback attributes, which determine when a value is checked for syntactic correctness, semantic correctness, and committed [9] We describe below communication attributes and communication rules that allow the coupling model to support all of the ....

.... value is guaranteed to be free of semantic errors and a value free of semantic errors is guaranteed to be free of syntax errors [9] Suite defines two attributes, called feedback attributes, which determine when a value is checked for syntactic correctness, semantic correctness, and committed [9]. We describe below communication attributes and communication rules that allow the coupling model to support all of the communication criteria described above. Transmitting Changes Consider first the criteria used by users to determine when changes made by them are transmitted to other users. ....

[Article contains additional citation context not shown here]

Prasun Dewan, "A Tour of the Suite User Interface Software," Proceedings of the 3rd ACM SIGGRAPH Symposium on User Interface Software and Technology, October 1990, pp. 57-65.

....can be defined once for all values in a group. The value groups are arranged in multiple intersecting hierarchies, and a subgroup is allowed to inherit attributes from its supergroup(s) An implementation of the model has been constructed for the Suite user interface development environment [3]. The specific value groups included in the model are motivated by our experience with developing interactive applications in various versions of Suite and its predecessor, Dost [2] The idea of classifying program values into groups and allowing specific groups to inherit properties from more ....

....Our contributions include application of this idea to the support of flexible displays of program data structures and new ways of grouping values and resolving multiple inheritance motivated by this application. Brief descriptions of parts of the model described here have appeared in References [3] and [2] SUITE We describe the abstract inheritance model using the concrete example of Suite. Interactive programs developed using Suite can display active values to users. An active value in Suite can be a character, integer, real, enumeration, subrange, record, variant record, array, sequence ....

[Article contains additional citation context not shown here]

Prasun Dewan, A Tour of the Suite User Interface Software, Proceedings of the 3rd ACM SIGGRAPH Symposium on User Interface Software and Technology, pp. 57-65 (October 1990).

....them to incrementally trade automation for flexibility and tailor only those aspects of the default collaboration scheme that are necessary to offer the desired collaboration scheme. The framework is an extension of the single user framework developed as part of the work on single user Suite [9], which provides high level and flexible support for implementing single user, editor based user interfaces. We have implemented the framework on top of single user Suite, thereby developing a new system, called multi user Suite, for supporting the development of multi user, editor based programs. ....

....by the first author as part of his dissertation work at the University of Wisconsin. We give here a brief summary of the main concepts used in the design of the system. More detailed descriptions of these concepts and motivation for supporting them are given in papers on single user Suite [9, 10, 14] and Dost [11] We also introduce in this section a running example, which is used to motivate and illustrate the concepts used in the design of both single user and multi user Suite. Single user) Suite differs from traditional interactive environments in several important ways. Users of Suite do ....

[Article contains additional citation context not shown here]

Prasun Dewan, "A Tour of the Suite User Interface Software," Proceedings of the 3rd ACM SIGGRAPH Symposium on User Interface Software and Technology, October 1990, pp. 57-65.

No context found.

Dewan, P. "A tour of the suite user interface software," Proceedings of 3rd ACM SIGGRAPH Symposium on User Interface Software and Technology, pages 57--65, Oct 1990.

No context found.

P. Dewan, A tour of the Suite User Interface Software, inProceedings UIST'90, ACM, 5765

No context found.

P. Dewan. A Tour of the Suite User Interface Software. Included in

No context found.

Dewan, P. (1990). A Tour of the Suite User Interface Software. In Hudson, S. E., editor, Proceedings of the ACM SIGGRAPH Symposium on User Interface Software and Technology (UIST'90), pages 57--65, Snowbird, Utah.

No context found.

Dewan, P, A tour of the Suite user interface software, in Proceedings of UIST'90 (1990), ACM Press, 57-65.

No context found.

P. Dewan. A Tour of the Suite User Interface Software. Included in

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