• Your recent searches
Bundle-PBib
11 results

 view release on metacpan or  search on metacpan

t/expected-sample-pbib.doc  view on Meta::CPAN 

interaction model\'94 described by {\field{\*\fldinst { HYPERLINK \\l SuiteCouplingUIs}}{\fldrslt {Dewan and Choudhary (1995)}}}.
\par As shown in figure }{\field{\*\fldinst {\insrsid12989836  REF fBasicModels \\h }{\insrsid12989836 {\*\datafield 08d0c9ea79f9bace118c8200aa004ba90b02000000080000000d0000006600420061007300690063004d006f00640065006c0073000000}}}{\fldrslt {
\lang1024\langfe1024\noproof\insrsid12989836 4}{\insrsid12989836 \_}{\lang1024\langfe1024\noproof\insrsid12989836 2}}}{\insrsid12989836 
, the interaction model defines a way to interact with all other basic models. This is necessary, as all models can define aspects and functions that can be represented for and a}{\insrsid12989836 c}{\insrsid12989836 
cessed by the user. For example, a data object like a \'93text\'94 object often has a directly attached view and controller, enabling direct interaction with the text; then, interaction and data model communicate d}{\insrsid12989836 i}{\insrsid129898...
rectly, bypassing user interface and application models. Alternatively, a \'93visual interaction area\'94 being part of the user interface model, provides functionality that has an immediate visual representation re}{\insrsid12989836 n}{\insrsid12989...
dered by the interaction model. In other cases, the interaction model will not access the data model d}{\insrsid12989836 i}{\insrsid12989836 
rectly. Instead, it is associated with an appropriate application model as a mediator to the data model. This way, the interaction style can be adapted depending on which application model is used to access a data model.
\par As an appropriate 
interaction style depends on the available interaction devices and the associated user interface, a suitable interaction model can be chosen depending on the environment and user-interface model. For visual-based interaction, an adapted version of th...
el-view-controller concept ({\field{\*\fldinst { HYPERLINK \\l MVCCookbook}}{\fldrslt {Krasner and Pope, 1988}}}; {\field{\*\fldinst { HYPERLINK \\l COASTooSyncGroupware}}{\fldrslt {Schuckmann {\i et al.}, 1996}}}) has proven su}{\insrsid12989836 c}{...
 of the model-view-controller concept is not further structured. It can refer to each of data, application, user interface, or environment model.
\par Passage defines an interactive visual representation (for the virtual part of the bridge) and physical a}{\insrsid12989836 c}{\insrsid12989836 
tions as input (placing objects on the physical part of the bridge). Consequently, its interaction model uses both a visual interaction model (see section }{\field{\*\fldinst {\insrsid12989836  REF sModelLayer \\r \\h }{\insrsid12989836 {\*\datafield...
08d0c9ea79f9bace118c8200aa004ba90b02000000080000000c00000073004d006f00640065006c004c0061007900650072000000}}}{\fldrslt {\insrsid12989836 5.2}}}{\insrsid12989836 ) and a sensor model providing the basis for detec}{\insrsid12989836 t}{\insrsid12989836 ...
ing physical o}{\insrsid12989836 b}{\insrsid12989836 jects (see section }{\field{\*\fldinst {\insrsid12989836  REF sSensorModel \\r \\h }{\insrsid12989836 {\*\datafield 
08d0c9ea79f9bace118c8200aa004ba90b02000000080000000d0000007300530065006e0073006f0072004d006f00640065006c000000}}}{\fldrslt {\insrsid12989836 6.1}}}{\insrsid12989836 ).
\par {\*\bkmkstart sConceptualSharing}{\*\bkmkstart _Toc19764442}{\listtext\pard\plain\s2 \f1\fs22\insrsid12989836 \hich\af1\dbch\af0\loch\f1 2.3\tab}}\pard\plain \s2\ql \fi-578\li578\ri0\sb120\sa60\keep\keepn\widctlpar
\jclisttab\tx576\hyphpar0\aspalpha\aspnum\faauto\ls128\ilvl1\outlinelevel1\adjustright\rin0\lin578\itap0 \f1\fs22\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Second Dimension: Coupling and Sharing{\*\bkmkend sConceptualSharing...
{\*\bkmkend _Toc19764442}
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Whenever multiple devices are involved in a software system, th

t/expected-sample-pbib.doc  view on Meta::CPAN 

{{\*\bkmkstart GroupKitAwarenessWidgets}{Gutwin, C., Roseman, M., and Greenberg, S., 1996. A Usability Study of Awareness Widgets in a Shared Workspace Groupware System. In: Proceedings of the ACM 1996 Conference on Computer Supported Cooperative Wor...
{\*\bkmkend GroupKitAwarenessWidgets}}\par
{{\*\bkmkstart HCIContextInfrastructure}{Hong, J. I. and Landay, J. A., 2001. An Infrastructure Approach to Context-Aware Computing, Human-Computer Interaction 16\~(2\endash 4), 287\endash 303.}
{\*\bkmkend HCIContextInfrastructure}}\par
{{\*\bkmkstart JacobsenSoftwareModelling}{Jacobsen, E. E., 2000. Concepts and Language Mechanisms in Software Modelling, Ph.D. thesis, Faculty of Science and Engineering, University of Southern Denmark. {\field{\*\fldinst { HYPERLINK http://www.mip.s...
{\*\bkmkend JacobsenSoftwareModelling}}\par
{{\*\bkmkstart JacobsonOOSE}{Jacobson, I., Christerson, M., Jonsson, P., and Övergaard, G., 1992. Object-Oriented Software Engineering, a Use Case Driven Approach, ACM Press, Addison Wesley.}
{\*\bkmkend JacobsonOOSE}}\par
{{\*\bkmkstart iRoomPointRight}{Johanson, B., Hutchins, G., Winograd, T., and Stone, M., 2002. PointRight: Experience with Flexible Input Redirection in Interactive Workspaces. In: Proceedings of the 15th annual ACM symposium on User interface softwa...
{\*\bkmkend iRoomPointRight}}\par
{{\*\bkmkstart MVCCookbook}{Krasner, G. E. and Pope, S. T., 1988. A Cookbook for Using the Model-View-Controller User Interface Paradigma in Smalltalk-80, Journal of Object Oriented Programming (JOOP) 1\~(3), 26\endash 49.}
{\*\bkmkend MVCCookbook}}\par
{{\*\bkmkstart ManifoldArchitecture}{Marsic, I., 2001. An Architecture for Heterogeneous Groupware Applications. In: Proceedings of the 23rd International Conference on Software Engineering, IEEE Computer Society Press, pp.\~475\endash 484. {\field{\...
{\*\bkmkend ManifoldArchitecture}}\par
{{\*\bkmkstart PACAMODEUS}{Nigay, L. and Coutaz, J., 1991. Building User Interfaces: Organizing Software Agents. In: Esprit'91 Conference Proceedings, ACM Press, New York, NY, pp.\~707\endash 719. {\field{\*\fldinst { HYPERLINK http://citeseer.nj.nec...
{\*\bkmkend PACAMODEUS}}\par
{{\*\bkmkstart InterlocusActivityAwareness}{Nomura, T., Hayashi, K., Hazama, T., and Gudmundson, S., 1998. Interlocus: Workspace Configuration Mechanisms for Activity Awareness. ACM Press, New York, NY, pp.\~19\endash 28.}
{\*\bkmkend InterlocusActivityAwareness}}\par
{{\*\bkmkstart NowackStructuresInteractions}{Nowack, P., 1999. Structures and Interactions\endash Characterizing Object-Oriented Software Architecture, Ph.D. thesis, Faculty of Software Engineering and Technology, University of Southern Denmark. {\fi...
{\*\bkmkend NowackStructuresInteractions}}\par
{{\*\bkmkstart XWebJoinCapture}{Olsen, Jr., D. R., Nielsen, S. T., and Parslow, D., 2001. Join and Capture: A Model for Nomadic Interaction. In: Proceedings of 14th Annual ACM Symposium on User Interface and Software Technology (UIST'01), vol.\~3, no...
{\*\bkmkend XWebJoinCapture}}\par

t/expected-sample-pbib.html  view on Meta::CPAN 

representation rendered by the interaction model. In other cases, the
interaction model will not access the data model directly. Instead,
it is associated with an appropriate application model as a mediator
to the data model. This way, the interaction style can be adapted
depending on which application model is used to access a data model.</P>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">As an appropriate
interaction style depends on the available interaction devices and
the associated user interface, a suitable interaction model can be
chosen depending on the environment and user-interface model. For
visual-based interaction, an adapted version of the
model-view-controller concept [[MVC-Cookbook],
[COAST-ooSyncGroupware]] has proven successful. However, the &ldquo;model&rdquo;
of the model-view-controller concept is not further structured. It
can refer to each of data, application, user interface, or
environment model.</P>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">Passage defines an
interactive visual representation (for the virtual part of the
bridge) and physical actions as input (placing objects on the
physical part of the bridge). Consequently, its interaction model
uses both a visual interaction model (see section ) and a sensor
model providing the basis for detecting physical objects (see section

t/expected-sample-pbib.html  view on Meta::CPAN 

Dewan, P. and Choudhary, R., 1995. Coupling the User Interfaces of a Multiuser Program, ACM Transactions on Computer-Human Interaction 2 (1), 1-39.
Dijkstra, E. W., 1968. The structure of the "THE"-multiprogramming system, Communications of the ACM 11 (5), 341-346. http://doi.acm.org/10.1145/363095.363143.
Edwards, W. K. and LaMarca, A., 1999. Balancing Generality and Specificity in Document Management Systems. In: INTERACT '99, IOS Press, pp. 187-195.
Gamma, E., Helm, R., Johnson, R., and Vlissides, J., 1995. Design Patterns: Elements of Reusable Object-Oriented Software, Addison Wesley.
Gutwin, C. and Greenberg, S., 1998. Design for Individuals, Design for Groups: Tradeoffs between power and workspace awareness. In: Proceedings of the ACM 1998 conference on Computer supported cooperative work, ACM Press, pp. 207-216. http://doi.acm....
Gutwin, C., Roseman, M., and Greenberg, S., 1996. A Usability Study of Awareness Widgets in a Shared Workspace Groupware System. In: Proceedings of the ACM 1996 Conference on Computer Supported Cooperative Work (CSCW'96), ACM Press, New York, NY, pp....
Hong, J. I. and Landay, J. A., 2001. An Infrastructure Approach to Context-Aware Computing, Human-Computer Interaction 16 (2--4), 287-303.
Jacobsen, E. E., 2000. Concepts and Language Mechanisms in Software Modelling, Ph.D. thesis, Faculty of Science and Engineering, University of Southern Denmark. http://www.mip.sdu.dk/sweat.
Jacobson, I., Christerson, M., Jonsson, P., and Övergaard, G., 1992. Object-Oriented Software Engineering, a Use Case Driven Approach, ACM Press, Addison Wesley.
Johanson, B., Hutchins, G., Winograd, T., and Stone, M., 2002. PointRight: Experience with Flexible Input Redirection in Interactive Workspaces. In: Proceedings of the 15th annual ACM symposium on User interface software and technology (UIST'02), vol...
Krasner, G. E. and Pope, S. T., 1988. A Cookbook for Using the Model-View-Controller User Interface Paradigma in Smalltalk-80, Journal of Object Oriented Programming (JOOP) 1 (3), 26-49.
Marsic, I., 2001. An Architecture for Heterogeneous Groupware Applications. In: Proceedings of the 23rd International Conference on Software Engineering, IEEE Computer Society Press, pp. 475-484. http://citeseer.nj.nec.com/marsic01architecture.html.
Nigay, L. and Coutaz, J., 1991. Building User Interfaces: Organizing Software Agents. In: Esprit'91 Conference Proceedings, ACM Press, New York, NY, pp. 707-719. http://citeseer.nj.nec.com/nigay91building.html, http://iihm.imag.fr/publs/1991/.
Nomura, T., Hayashi, K., Hazama, T., and Gudmundson, S., 1998. Interlocus: Workspace Configuration Mechanisms for Activity Awareness. In: Proceedings of the ACM 1998 Conference on Computer Supported Cooperative Work (CSCW'98), ACM Press, New York, NY...
Nowack, P., 1999. Structures and Interactions - Characterizing Object-Oriented Software Architecture, Ph.D. thesis, Faculty of Software Engineering and Technology, University of Southern Denmark. http://www.mip.sdu.dk/sweat.
Olsen, Jr., D. R., Nielsen, S. T., and Parslow, D., 2001. Join and Capture: A Model for Nomadic Interaction. In: Proceedings of 14th Annual ACM Symposium on User Interface and Software Technology (UIST'01), vol. 3, no. 2 in CHI Letters, ACM Press, Ne...
Parnas, D. L., 1972. On the criteria to be used in decomposing systems into modules, Communications of the ACM 15 (12), 1053-1058. http://doi.acm.org/10.1145/361598.361623.
Patterson, J. F., 1991. Comparing the Programming Demands of Single-User and Multi-User Applications. In: Proceedings of ACM SIGGRAPH Symposium on User Interface Software and Technology (UIST'91), ACM Press, New York, NY, pp. 87-94.
Phillips, W. G., 1999. Architectures for Synchronous Groupware, Tech. Rep., Queen's University, Kingston, Ontario K7L 3N6. http://phillips.rmc.ca/greg/pub/.
Pier, K. and Landay, J. A., 1992. Issues for Location-independent Interfaces, Tech. Rep., Xerox PARC, Palo Alto, CA, USA. http://www.cs.berkeley.edu/~landay/research/publications/LII.ps, http://citeseer.nj.nec.com/pier92issues.html.
Prante, T., 2001. Designing for Usable Disappearance - Mediating Coherence, Scope, and Orientation. In: Workshop Proceedings "Distributed and Disappearing User Interfaces in Ubiquitous Computing", ACM CHI'01. http://www.teco.edu/chi2001ws/proceedings...

t/expected-sample-pbib.rtf  view on Meta::CPAN 

interaction model\'94 described by {\field{\*\fldinst { HYPERLINK \\l SuiteCouplingUIs}}{\fldrslt {Dewan and Choudhary (1995)}}}.
\par As shown in figure }{\field{\*\fldinst {\insrsid12989836  REF fBasicModels \\h }{\insrsid12989836 {\*\datafield 08d0c9ea79f9bace118c8200aa004ba90b02000000080000000d0000006600420061007300690063004d006f00640065006c0073000000}}}{\fldrslt {
\lang1024\langfe1024\noproof\insrsid12989836 4}{\insrsid12989836 \_}{\lang1024\langfe1024\noproof\insrsid12989836 2}}}{\insrsid12989836 
, the interaction model defines a way to interact with all other basic models. This is necessary, as all models can define aspects and functions that can be represented for and a}{\insrsid12989836 c}{\insrsid12989836 
cessed by the user. For example, a data object like a \'93text\'94 object often has a directly attached view and controller, enabling direct interaction with the text; then, interaction and data model communicate d}{\insrsid12989836 i}{\insrsid129898...
rectly, bypassing user interface and application models. Alternatively, a \'93visual interaction area\'94 being part of the user interface model, provides functionality that has an immediate visual representation re}{\insrsid12989836 n}{\insrsid12989...
dered by the interaction model. In other cases, the interaction model will not access the data model d}{\insrsid12989836 i}{\insrsid12989836 
rectly. Instead, it is associated with an appropriate application model as a mediator to the data model. This way, the interaction style can be adapted depending on which application model is used to access a data model.
\par As an appropriate 
interaction style depends on the available interaction devices and the associated user interface, a suitable interaction model can be chosen depending on the environment and user-interface model. For visual-based interaction, an adapted version of th...
el-view-controller concept ({\field{\*\fldinst { HYPERLINK \\l MVCCookbook}}{\fldrslt {Krasner and Pope, 1988}}}; {\field{\*\fldinst { HYPERLINK \\l COASTooSyncGroupware}}{\fldrslt {Schuckmann {\i et al.}, 1996}}}) has proven su}{\insrsid12989836 c}{...
 of the model-view-controller concept is not further structured. It can refer to each of data, application, user interface, or environment model.
\par Passage defines an interactive visual representation (for the virtual part of the bridge) and physical a}{\insrsid12989836 c}{\insrsid12989836 
tions as input (placing objects on the physical part of the bridge). Consequently, its interaction model uses both a visual interaction model (see section }{\field{\*\fldinst {\insrsid12989836  REF sModelLayer \\r \\h }{\insrsid12989836 {\*\datafield...
08d0c9ea79f9bace118c8200aa004ba90b02000000080000000c00000073004d006f00640065006c004c0061007900650072000000}}}{\fldrslt {\insrsid12989836 5.2}}}{\insrsid12989836 ) and a sensor model providing the basis for detec}{\insrsid12989836 t}{\insrsid12989836 ...
ing physical o}{\insrsid12989836 b}{\insrsid12989836 jects (see section }{\field{\*\fldinst {\insrsid12989836  REF sSensorModel \\r \\h }{\insrsid12989836 {\*\datafield 
08d0c9ea79f9bace118c8200aa004ba90b02000000080000000d0000007300530065006e0073006f0072004d006f00640065006c000000}}}{\fldrslt {\insrsid12989836 6.1}}}{\insrsid12989836 ).
\par {\*\bkmkstart sConceptualSharing}{\*\bkmkstart _Toc19764442}{\listtext\pard\plain\s2 \f1\fs22\insrsid12989836 \hich\af1\dbch\af0\loch\f1 2.3\tab}}\pard\plain \s2\ql \fi-578\li578\ri0\sb120\sa60\keep\keepn\widctlpar
\jclisttab\tx576\hyphpar0\aspalpha\aspnum\faauto\ls128\ilvl1\outlinelevel1\adjustright\rin0\lin578\itap0 \f1\fs22\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Second Dimension: Coupling and Sharing{\*\bkmkend sConceptualSharing...
{\*\bkmkend _Toc19764442}
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Whenever multiple devices are involved in a software system, th

t/expected-sample-pbib.rtf  view on Meta::CPAN 

{{\*\bkmkstart GroupKitAwarenessWidgets}{Gutwin, C., Roseman, M., and Greenberg, S., 1996. A Usability Study of Awareness Widgets in a Shared Workspace Groupware System. In: Proceedings of the ACM 1996 Conference on Computer Supported Cooperative Wor...
{\*\bkmkend GroupKitAwarenessWidgets}}\par
{{\*\bkmkstart HCIContextInfrastructure}{Hong, J. I. and Landay, J. A., 2001. An Infrastructure Approach to Context-Aware Computing, Human-Computer Interaction 16\~(2\endash 4), 287\endash 303.}
{\*\bkmkend HCIContextInfrastructure}}\par
{{\*\bkmkstart JacobsenSoftwareModelling}{Jacobsen, E. E., 2000. Concepts and Language Mechanisms in Software Modelling, Ph.D. thesis, Faculty of Science and Engineering, University of Southern Denmark. {\field{\*\fldinst { HYPERLINK http://www.mip.s...
{\*\bkmkend JacobsenSoftwareModelling}}\par
{{\*\bkmkstart JacobsonOOSE}{Jacobson, I., Christerson, M., Jonsson, P., and Övergaard, G., 1992. Object-Oriented Software Engineering, a Use Case Driven Approach, ACM Press, Addison Wesley.}
{\*\bkmkend JacobsonOOSE}}\par
{{\*\bkmkstart iRoomPointRight}{Johanson, B., Hutchins, G., Winograd, T., and Stone, M., 2002. PointRight: Experience with Flexible Input Redirection in Interactive Workspaces. In: Proceedings of the 15th annual ACM symposium on User interface softwa...
{\*\bkmkend iRoomPointRight}}\par
{{\*\bkmkstart MVCCookbook}{Krasner, G. E. and Pope, S. T., 1988. A Cookbook for Using the Model-View-Controller User Interface Paradigma in Smalltalk-80, Journal of Object Oriented Programming (JOOP) 1\~(3), 26\endash 49.}
{\*\bkmkend MVCCookbook}}\par
{{\*\bkmkstart ManifoldArchitecture}{Marsic, I., 2001. An Architecture for Heterogeneous Groupware Applications. In: Proceedings of the 23rd International Conference on Software Engineering, IEEE Computer Society Press, pp.\~475\endash 484. {\field{\...
{\*\bkmkend ManifoldArchitecture}}\par
{{\*\bkmkstart PACAMODEUS}{Nigay, L. and Coutaz, J., 1991. Building User Interfaces: Organizing Software Agents. In: Esprit'91 Conference Proceedings, ACM Press, New York, NY, pp.\~707\endash 719. {\field{\*\fldinst { HYPERLINK http://citeseer.nj.nec...
{\*\bkmkend PACAMODEUS}}\par
{{\*\bkmkstart InterlocusActivityAwareness}{Nomura, T., Hayashi, K., Hazama, T., and Gudmundson, S., 1998. Interlocus: Workspace Configuration Mechanisms for Activity Awareness. In: Proceedings of the ACM 1998 Conference on Computer Supported Coopera...
{\*\bkmkend InterlocusActivityAwareness}}\par
{{\*\bkmkstart NowackStructuresInteractions}{Nowack, P., 1999. Structures and Interactions\endash Characterizing Object-Oriented Software Architecture, Ph.D. thesis, Faculty of Software Engineering and Technology, University of Southern Denmark. {\fi...
{\*\bkmkend NowackStructuresInteractions}}\par
{{\*\bkmkstart XWebJoinCapture}{Olsen, Jr., D. R., Nielsen, S. T., and Parslow, D., 2001. Join and Capture: A Model for Nomadic Interaction. In: Proceedings of 14th Annual ACM Symposium on User Interface and Software Technology (UIST'01), vol.\~3, no...
{\*\bkmkend XWebJoinCapture}}\par

t/expected-sample-pbib.txt  view on Meta::CPAN 

Dewan, P. and Choudhary, R., 1995. Coupling the User Interfaces of a Multiuser Program, ACM Transactions on Computer-Human Interaction 2 (1), 1-39.
Dijkstra, E. W., 1968. The structure of the "THE"-multiprogramming system, Communications of the ACM 11 (5), 341-346. http://doi.acm.org/10.1145/363095.363143.
Edwards, W. K. and LaMarca, A., 1999. Balancing Generality and Specificity in Document Management Systems. In: INTERACT '99, IOS Press, pp. 187-195.
Gamma, E., Helm, R., Johnson, R., and Vlissides, J., 1995. Design Patterns: Elements of Reusable Object-Oriented Software, Addison Wesley.
Gutwin, C. and Greenberg, S., 1998. Design for Individuals, Design for Groups: Tradeoffs between power and workspace awareness. In: Proceedings of the ACM 1998 conference on Computer supported cooperative work, ACM Press, pp. 207-216. http://doi.acm....
Gutwin, C., Roseman, M., and Greenberg, S., 1996. A Usability Study of Awareness Widgets in a Shared Workspace Groupware System. In: Proceedings of the ACM 1996 Conference on Computer Supported Cooperative Work (CSCW'96), ACM Press, New York, NY, pp....
Hong, J. I. and Landay, J. A., 2001. An Infrastructure Approach to Context-Aware Computing, Human-Computer Interaction 16 (2--4), 287-303.
Jacobsen, E. E., 2000. Concepts and Language Mechanisms in Software Modelling, Ph.D. thesis, Faculty of Science and Engineering, University of Southern Denmark. http://www.mip.sdu.dk/sweat.
Jacobson, I., Christerson, M., Jonsson, P., and Övergaard, G., 1992. Object-Oriented Software Engineering, a Use Case Driven Approach, ACM Press, Addison Wesley.
Johanson, B., Hutchins, G., Winograd, T., and Stone, M., 2002. PointRight: Experience with Flexible Input Redirection in Interactive Workspaces. In: Proceedings of the 15th annual ACM symposium on User interface software and technology (UIST'02), vol...
Krasner, G. E. and Pope, S. T., 1988. A Cookbook for Using the Model-View-Controller User Interface Paradigma in Smalltalk-80, Journal of Object Oriented Programming (JOOP) 1 (3), 26-49.
Marsic, I., 2001. An Architecture for Heterogeneous Groupware Applications. In: Proceedings of the 23rd International Conference on Software Engineering, IEEE Computer Society Press, pp. 475-484. http://citeseer.nj.nec.com/marsic01architecture.html.
Nigay, L. and Coutaz, J., 1991. Building User Interfaces: Organizing Software Agents. In: Esprit'91 Conference Proceedings, ACM Press, New York, NY, pp. 707-719. http://citeseer.nj.nec.com/nigay91building.html, http://iihm.imag.fr/publs/1991/.
Nomura, T., Hayashi, K., Hazama, T., and Gudmundson, S., 1998. Interlocus: Workspace Configuration Mechanisms for Activity Awareness. In: Proceedings of the ACM 1998 Conference on Computer Supported Cooperative Work (CSCW'98), ACM Press, New York, NY...
Nowack, P., 1999. Structures and Interactions - Characterizing Object-Oriented Software Architecture, Ph.D. thesis, Faculty of Software Engineering and Technology, University of Southern Denmark. http://www.mip.sdu.dk/sweat.
Olsen, Jr., D. R., Nielsen, S. T., and Parslow, D., 2001. Join and Capture: A Model for Nomadic Interaction. In: Proceedings of 14th Annual ACM Symposium on User Interface and Software Technology (UIST'01), vol. 3, no. 2 in CHI Letters, ACM Press, Ne...
Parnas, D. L., 1972. On the criteria to be used in decomposing systems into modules, Communications of the ACM 15 (12), 1053-1058. http://doi.acm.org/10.1145/361598.361623.
Patterson, J. F., 1991. Comparing the Programming Demands of Single-User and Multi-User Applications. In: Proceedings of ACM SIGGRAPH Symposium on User Interface Software and Technology (UIST'91), ACM Press, New York, NY, pp. 87-94.
Phillips, W. G., 1999. Architectures for Synchronous Groupware, Tech. Rep., Queen's University, Kingston, Ontario K7L 3N6. http://phillips.rmc.ca/greg/pub/.
Pier, K. and Landay, J. A., 1992. Issues for Location-independent Interfaces, Tech. Rep., Xerox PARC, Palo Alto, CA, USA. http://www.cs.berkeley.edu/~landay/research/publications/LII.ps, http://citeseer.nj.nec.com/pier92issues.html.
Prante, T., 2001. Designing for Usable Disappearance - Mediating Coherence, Scope, and Orientation. In: Workshop Proceedings "Distributed and Disappearing User Interfaces in Ubiquitous Computing", ACM CHI'01. http://www.teco.edu/chi2001ws/proceedings...

t/expected-sample-pbib.xml  view on Meta::CPAN 

Dewan, P. and Choudhary, R., 1995. Coupling the User Interfaces of a Multiuser Program, ACM Transactions on Computer-Human Interaction 2 (1), 1-39.
Dijkstra, E. W., 1968. The structure of the "THE"-multiprogramming system, Communications of the ACM 11 (5), 341-346. http://doi.acm.org/10.1145/363095.363143.
Edwards, W. K. and LaMarca, A., 1999. Balancing Generality and Specificity in Document Management Systems. In: INTERACT '99, IOS Press, pp. 187-195.
Gamma, E., Helm, R., Johnson, R., and Vlissides, J., 1995. Design Patterns: Elements of Reusable Object-Oriented Software, Addison Wesley.
Gutwin, C. and Greenberg, S., 1998. Design for Individuals, Design for Groups: Tradeoffs between power and workspace awareness. In: Proceedings of the ACM 1998 conference on Computer supported cooperative work, ACM Press, pp. 207-216. http://doi.acm....
Gutwin, C., Roseman, M., and Greenberg, S., 1996. A Usability Study of Awareness Widgets in a Shared Workspace Groupware System. In: Proceedings of the ACM 1996 Conference on Computer Supported Cooperative Work (CSCW'96), ACM Press, New York, NY, pp....
Hong, J. I. and Landay, J. A., 2001. An Infrastructure Approach to Context-Aware Computing, Human-Computer Interaction 16 (2--4), 287-303.
Jacobsen, E. E., 2000. Concepts and Language Mechanisms in Software Modelling, Ph.D. thesis, Faculty of Science and Engineering, University of Southern Denmark. http://www.mip.sdu.dk/sweat.
Jacobson, I., Christerson, M., Jonsson, P., and Övergaard, G., 1992. Object-Oriented Software Engineering, a Use Case Driven Approach, ACM Press, Addison Wesley.
Johanson, B., Hutchins, G., Winograd, T., and Stone, M., 2002. PointRight: Experience with Flexible Input Redirection in Interactive Workspaces. In: Proceedings of the 15th annual ACM symposium on User interface software and technology (UIST'02), vol...
Krasner, G. E. and Pope, S. T., 1988. A Cookbook for Using the Model-View-Controller User Interface Paradigma in Smalltalk-80, Journal of Object Oriented Programming (JOOP) 1 (3), 26-49.
Marsic, I., 2001. An Architecture for Heterogeneous Groupware Applications. In: Proceedings of the 23rd International Conference on Software Engineering, IEEE Computer Society Press, pp. 475-484. http://citeseer.nj.nec.com/marsic01architecture.html.
Nigay, L. and Coutaz, J., 1991. Building User Interfaces: Organizing Software Agents. In: Esprit'91 Conference Proceedings, ACM Press, New York, NY, pp. 707-719. http://citeseer.nj.nec.com/nigay91building.html, http://iihm.imag.fr/publs/1991/.
Nomura, T., Hayashi, K., Hazama, T., and Gudmundson, S., 1998. Interlocus: Workspace Configuration Mechanisms for Activity Awareness. In: Proceedings of the ACM 1998 Conference on Computer Supported Cooperative Work (CSCW'98), ACM Press, New York, NY...
Nowack, P., 1999. Structures and Interactions - Characterizing Object-Oriented Software Architecture, Ph.D. thesis, Faculty of Software Engineering and Technology, University of Southern Denmark. http://www.mip.sdu.dk/sweat.
Olsen, Jr., D. R., Nielsen, S. T., and Parslow, D., 2001. Join and Capture: A Model for Nomadic Interaction. In: Proceedings of 14th Annual ACM Symposium on User Interface and Software Technology (UIST'01), vol. 3, no. 2 in CHI Letters, ACM Press, Ne...
Parnas, D. L., 1972. On the criteria to be used in decomposing systems into modules, Communications of the ACM 15 (12), 1053-1058. http://doi.acm.org/10.1145/361598.361623.
Patterson, J. F., 1991. Comparing the Programming Demands of Single-User and Multi-User Applications. In: Proceedings of ACM SIGGRAPH Symposium on User Interface Software and Technology (UIST'91), ACM Press, New York, NY, pp. 87-94.
Phillips, W. G., 1999. Architectures for Synchronous Groupware, Tech. Rep., Queen's University, Kingston, Ontario K7L 3N6. http://phillips.rmc.ca/greg/pub/.
Pier, K. and Landay, J. A., 1992. Issues for Location-independent Interfaces, Tech. Rep., Xerox PARC, Palo Alto, CA, USA. http://www.cs.berkeley.edu/~landay/research/publications/LII.ps, http://citeseer.nj.nec.com/pier92issues.html.
Prante, T., 2001. Designing for Usable Disappearance - Mediating Coherence, Scope, and Orientation. In: Workshop Proceedings "Distributed and Disappearing User Interfaces in Ubiquitous Computing", ACM CHI'01. http://www.teco.edu/chi2001ws/proceedings...

t/sample.bib  view on Meta::CPAN 

   year = {2000},
   isbn = {3-540-41093-7},
   note = {The short papers are available in the journal Personal and Ubiquitous Computing http://www.personal-ubicomp.com},
   Category = {UbiComp},
   PBibNote = {http://www.personal-ubicomp.com/huc2k/papers-programme.pdf},
   ExportDate = {2003-06-16 11:44:53},
   Identifier = {HUC'00},
   BibDate = {Sun Dec  8 17:44:52 2002},
}

@article{MVC-Cookbook,
   author = {G. E. Krasner and S. T. Pope},
   title = {A Cookbook for Using the Model-View-Controller User Interface Paradigma in Smalltalk-80},
   journal = {Journal of Object Oriented Programming (JOOP)},
   volume = {1},
   number = {3},
   pages = {26-49},
   year = {1988},
   keywords = {MVC},
   Category = {HCI.SW.Model},
   Recommendation = {++(\#\#)},
   BibDate = {2003-06-16 11:44:53},
   ExportDate = {2003-06-16 11:44:53},

t/sample.html  view on Meta::CPAN 

representation rendered by the interaction model. In other cases, the
interaction model will not access the data model directly. Instead,
it is associated with an appropriate application model as a mediator
to the data model. This way, the interaction style can be adapted
depending on which application model is used to access a data model.</P>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">As an appropriate
interaction style depends on the available interaction devices and
the associated user interface, a suitable interaction model can be
chosen depending on the environment and user-interface model. For
visual-based interaction, an adapted version of the
model-view-controller concept [[MVC-Cookbook],
[COAST-ooSyncGroupware]] has proven successful. However, the &ldquo;model&rdquo;
of the model-view-controller concept is not further structured. It
can refer to each of data, application, user interface, or
environment model.</P>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">Passage defines an
interactive visual representation (for the virtual part of the
bridge) and physical actions as input (placing objects on the
physical part of the bridge). Consequently, its interaction model
uses both a visual interaction model (see section ) and a sensor
model providing the basis for detecting physical objects (see section

t/sample.rtf  view on Meta::CPAN 

interaction model\'94 described by [ :inline | [Suite-CouplingUIs]].
\par As shown in figure }{\field{\*\fldinst {\insrsid12989836  REF fBasicModels \\h }{\insrsid12989836 {\*\datafield 08d0c9ea79f9bace118c8200aa004ba90b02000000080000000d0000006600420061007300690063004d006f00640065006c0073000000}}}{\fldrslt {
\lang1024\langfe1024\noproof\insrsid12989836 4}{\insrsid12989836 \_}{\lang1024\langfe1024\noproof\insrsid12989836 2}}}{\insrsid12989836 
, the interaction model defines a way to interact with all other basic models. This is necessary, as all models can define aspects and functions that can be represented for and a}{\insrsid12989836 c}{\insrsid12989836 
cessed by the user. For example, a data object like a \'93text\'94 object often has a directly attached view and controller, enabling direct interaction with the text; then, interaction and data model communicate d}{\insrsid12989836 i}{\insrsid129898...
rectly, bypassing user interface and application models. Alternatively, a \'93visual interaction area\'94 being part of the user interface model, provides functionality that has an immediate visual representation re}{\insrsid12989836 n}{\insrsid12989...
dered by the interaction model. In other cases, the interaction model will not access the data model d}{\insrsid12989836 i}{\insrsid12989836 
rectly. Instead, it is associated with an appropriate application model as a mediator to the data model. This way, the interaction style can be adapted depending on which application model is used to access a data model.
\par As an appropriate 
interaction style depends on the available interaction devices and the associated user interface, a suitable interaction model can be chosen depending on the environment and user-interface model. For visual-based interaction, an adapted version of th...
el-view-controller concept [[MVC-Cookbook], [COAST-ooSyncGroupware]] has proven su}{\insrsid12989836 c}{\insrsid12989836 cessful. However, the \'93model\'94
 of the model-view-controller concept is not further structured. It can refer to each of data, application, user interface, or environment model.
\par Passage defines an interactive visual representation (for the virtual part of the bridge) and physical a}{\insrsid12989836 c}{\insrsid12989836 
tions as input (placing objects on the physical part of the bridge). Consequently, its interaction model uses both a visual interaction model (see section }{\field{\*\fldinst {\insrsid12989836  REF sModelLayer \\r \\h }{\insrsid12989836 {\*\datafield...
08d0c9ea79f9bace118c8200aa004ba90b02000000080000000c00000073004d006f00640065006c004c0061007900650072000000}}}{\fldrslt {\insrsid12989836 5.2}}}{\insrsid12989836 ) and a sensor model providing the basis for detec}{\insrsid12989836 t}{\insrsid12989836 ...
ing physical o}{\insrsid12989836 b}{\insrsid12989836 jects (see section }{\field{\*\fldinst {\insrsid12989836  REF sSensorModel \\r \\h }{\insrsid12989836 {\*\datafield 
08d0c9ea79f9bace118c8200aa004ba90b02000000080000000d0000007300530065006e0073006f0072004d006f00640065006c000000}}}{\fldrslt {\insrsid12989836 6.1}}}{\insrsid12989836 ).
\par {\*\bkmkstart sConceptualSharing}{\*\bkmkstart _Toc19764442}{\listtext\pard\plain\s2 \f1\fs22\insrsid12989836 \hich\af1\dbch\af0\loch\f1 2.3\tab}}\pard\plain \s2\ql \fi-578\li578\ri0\sb120\sa60\keep\keepn\widctlpar
\jclisttab\tx576\hyphpar0\aspalpha\aspnum\faauto\ls128\ilvl1\outlinelevel1\adjustright\rin0\lin578\itap0 \f1\fs22\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Second Dimension: Coupling and Sharing{\*\bkmkend sConceptualSharing...
{\*\bkmkend _Toc19764442}
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Whenever multiple devices are involved in a software system, th

t/sample.txt  view on Meta::CPAN 

Environment Model: Context Awareness
One major property of ubiquitous computing environments is the heterogeneity of the available devices. In order to provide a coherent user experience [[DisappearingUI-CoherenceScope]], the "system must have a deeper understanding of the physical spac...
Therefore, the environment model is the representation of relevant parts of the "real" world. On one hand, this includes a description of which devices are used, how they are configured, and which capabilities they have. This is the direct hardware e...
In addition, other aspects can be included if they can influence the behavior of the software. Necessarily, it has to be possible to measure their relevant properties with sensors. Depending on detected changes in the physical environment, further ac...
The Passage system is an example of how to react upon changes in the physical environment. As mentioned, the virtual part of the bridge is shown as soon as a physical object is detected on the physical part of the bridge. Thus, Passage needs to keep ...
Besides the physical environment, other contextual information – such as the current task, project, or presence of co-workers – could influence the behavior of the software, so long as this information is available to the application. This part refer...
Software with functionality depending on physical objects and their properties, or other aspects of the user's environment (req. ) is called context-aware [[ContextToolkit-AppDevelopment]]. There is a strong need for context-aware applications in ubi...
Interaction Model: Presentation and Interaction
To be able to support different styles of interaction (req. , ), the interaction model specifies how different interaction styles can be defined. The term used here describes a part of the software architecture, and should not be confused with the "i...
As shown in figure 4-2.2, the interaction model defines a way to interact with all other basic models. This is necessary, as all models can define aspects and functions that can be represented for and accessed by the user. For example, a data object ...
As an appropriate interaction style depends on the available interaction devices and the associated user interface, a suitable interaction model can be chosen depending on the environment and user-interface model. For visual-based interaction, an ada...
Passage defines an interactive visual representation (for the virtual part of the bridge) and physical actions as input (placing objects on the physical part of the bridge). Consequently, its interaction model uses both a visual interaction model (se...
2.3Second Dimension: Coupling and Sharing
Whenever multiple devices are involved in a software system, the question arises, which parts of the system should be local to a device or shared between several. This has to be clarified for both the application code and its state. While distributin...
Today, many applications still run entirely local to a single computer, or access only data that is distributed over a network. Aiming at synchronous collaboration, crucial aspects of traditional CSCW systems are access to shared data and coupling th...
In the context of ubiquitous computing environments, this view has to be extended. In addition to data and application, also information about the physical environment, e.g., the presence of nearby users or other available interaction devices, has to...
As discussed above, in a ubiquitous computing environment elements of the user interface can be distributed among several machines (req. ) or among different devices (req. ). Based on the separation of concerns that has been previously identified, De...
Depending on how much state is shared, the degree of coupling can be controlled. If all involved user interface and editing state is shared, a tightly coupled collaboration mode is realized; if only the same data model is shared, users work loosely c...
Even, if some models are not coupled, one can profit from sharing environment, user interface, and application models. As the information encapsulated in the models is accessible to all clients, it is possible to provide awareness information in the ...
Beyond the provision of awareness in CSCW systems, sharing the environment model allows a new kind of awareness for ubiquitous computing environments. The information embodied in the environment model can be used to give environmental awareness.
This section discusses the aspects of sharing the basic models. Before starting a detailed discussion, it has to be noted that "sharing" can be implemented in many different ways. In the case of collaborating devices with quite varying properties – e...

t/sample.xml  view on Meta::CPAN 

<para>Therefore, the environment model is the representation of relevant parts of the “real” world. On one hand, this includes a description of which devices are used, how they are configured, and which capabilities they have. This is the direct ...
<para>In addition, other aspects can be included if they can influence the behavior of the software. Necessarily, it has to be possible to measure their relevant properties with sensors. Depending on detected changes in the physical environment, furt...
<para>The Passage system is an example of how to react upon changes in the physical environment. As mentioned, the virtual part of the bridge is shown as soon as a physical object is detected on the physical part of the bridge. Thus, Passage needs to...
<para>Besides the physical environment, other contextual information – such as the current task, project, or presence of co-workers – could influence the behavior of the software, so long as this information is available to the application. This ...
<para>Software with functionality depending on physical objects and their properties, or other aspects of the user’s environment (req. ) is called context-aware [[ContextToolkit-AppDevelopment]]. There is a strong need for context-aware application...
      <para>However, using detected context to trigger functionality always has the danger of relying on misinterpreted information, which can be very annoying for users.</para>
</footnote> Therefore, the environment model must be capable of expressing relevant information, such as spatial relationships between physical objects.</para>
<para>Interaction Model: Presentation and Interaction</para>
<para>To be able to support different styles of interaction (req. , ), the interaction model specifies how different interaction styles can be defined. The term used here describes a part of the software architecture, and should not be confused with ...
<para>As shown in figure 4-2.2, the interaction model defines a way to interact with all other basic models. This is necessary, as all models can define aspects and functions that can be represented for and accessed by the user. For example, a data o...
<para>As an appropriate interaction style depends on the available interaction devices and the associated user interface, a suitable interaction model can be chosen depending on the environment and user-interface model. For visual-based interaction, ...
<para>Passage defines an interactive visual representation (for the virtual part of the bridge) and physical actions as input (placing objects on the physical part of the bridge). Consequently, its interaction model uses both a visual interaction mod...
<para>Whenever multiple devices are involved in a software system, the question arises, which parts of the system should be local to a device or shared between several. This has to be clarified for both the application code and its state. While distr...
<para>Today, many applications still run entirely local to a single computer, or access only data that is distributed over a network. Aiming at synchronous collaboration, crucial aspects of traditional CSCW systems are access to shared data and coupl...
<para>In the context of ubiquitous computing environments, this view has to be extended. In addition to data and application, also information about the physical environment, e.g., the presence of nearby users or other available interaction devices, ...
<para>As discussed above, in a ubiquitous computing environment elements of the user interface can be distributed among several machines (req. ) or among different devices (req. ). Based on the separation of concerns that has been previously identifi...
<para>Depending on how much state is shared, the degree of coupling can be controlled. If all involved user interface and editing state is shared, a tightly coupled collaboration mode is realized; if only the same data model is shared, users work loo...
<para>Even, if some models are not coupled, one can profit from sharing environment, user interface, and application models. As the information encapsulated in the models is accessible to all clients, it is possible to provide awareness information i...
<para>Beyond the provision of awareness in CSCW systems, sharing the environment model allows a new kind of awareness for ubiquitous computing environments. The information embodied in the environment model can be used to give environmental awareness...
<para>This section discusses the aspects of sharing the basic models. Before starting a detailed discussion, it has to be noted that “sharing” can be implemented in many different ways. In the case of collaborating devices with quite varying prop...
<para>Sharing the Data Model: Collaborative Data Access</para>



( run in 0.712 second using v1.01-cache-2.11-cpan-e9199f4ba4c )