think-cell technical report TC2003/01 A GUI-based Interaction ...

More documents

Recommendations

Info

4.3 Specifying the User Interface INTERACTION CONCEPT z-Axis (projection) (a) Appearance on the slide z = 8 z = 6 z = 7 z = 5 (c) Another possible z-order z-Axis z = 7 z = 8 z = 6 z = 8 (b) Possible z-order z = 7 z = 6 z = 5 z = 5 (d) Yet another possible z-order Figure 34: An example for an arrangement of shapes with wrong z-order (a) Appearance on the slide z = 8 z = 7 z = 5 (b) “Side view” z = 6 Figure 35: The same example as in Fig. 34 with the z-order corrected by a colored hairline between the shapes. Badros et al. [BNB00] suggest a similar representation for constraints between windows in a WIMP environment. Element-Specific Constraints Some more complex smart elements have specific constraints or settings that do not apply to other types of shapes. In the current prototype, each smart element has a contextual menu associated with it (Fig. 15). A right mouse button click opens the contextual menu of the selected smart element or elements. Depending on the type of the smart element, the contextual menu offers buttons for color, font size and the like. In the case of charts, for example, there are also options to turn labels and other specific features on or off. 68
5 Implementation IMPLEMENTATION The prototype that was developed in the course of this work is based on a product by think-cell Software. The think-cell product is an add-in to Microsoft PowerPoint that uses a variety of techniques to interact with PowerPoint (Fig. 36). The Micro- soft Office Object Model and the Active Document Interface, which are designed for add-ins like the think-cell product, allow only limited access to the PowerPoint engine. Therefore, in the think-cell implementation, these techniques are supple- mented by Window Subclassing for message interception. Moreover, think-cell uses DirectX to create custom on-screen UI widgets. My implementation does not make immediate use of any of the techniques men- tioned. The classes that I implemented merely interact with the high-level C++ programming interface of the think-cell product and are compiled as part of that product. User Interface think-cell Add-In PowerPoint Excel Win 32 API DirectX Object Model Active Document Interface Active Document Interface Office Object Model SubclassingOffice Window Figure 36: The think-cell architecture uses a variety of techniques to interact with PowerPoint. 5.1 Program Architecture To get an understanding of the program architecture in general and the user interface code in particular, in this section a number of structural diagrams are discussed in turn. I begin with an overview of the major entities and relations, followed by a close-up look at a hierarchy of UI-related subclasses and finally I examine some interaction scenarios involving a couple of classes. 5.1.1 Overview: Entity-Relation Figure 37 provides an overview of the most important inter-class relationships of the C++ code. The CPPTFrame class relates to a runtime instance of PowerPoint. It contains presentations and document windows. PowerPoint is an MDI 11 application and each instance of CPPTDocWnd relates to a runtime document window. Both classes intercept Windows messages, most prominently repaint requests and user input like mouse movements and key presses. They process and forward those messages at application or window level, respectively. 11 Multiple Document Interface (MDI): A single running application instance can open and edit multiple independent documents at a time. 69
Page 1 and 2:
think-cell technical report TC2003/
Page 3 and 4:
Contents List of Figures 5 1 Introd
Page 5 and 6:
List of Figures 1 The consultant’
Page 7 and 8:
1 Introduction INTRODUCTION “Layo
Page 9 and 10:
2 Field Study FIELD STUDY Jeff Hawk
Page 11 and 12:
2.1 Qualitative Aspects FIELD STUDY
Page 13 and 14:
Page 15 and 16:
Page 17 and 18: 2.1 Qualitative Aspects FIELD STUDY
Page 19 and 20: 2.2 Quantitative Aspects FIELD STUD
Page 25 and 26: 3 State of the Art STATE OF THE ART
Page 27 and 28: 3.1 User Interfaces for Layout Spec
Page 29 and 30: 3.2 Computer Supported Layout STATE
Page 31 and 32: 3.2 Computer Supported Layout STATE
Page 33 and 34: 3.3 State of the Art - Résumé STA
Page 35 and 36: 4.1 A New Approach to Slide Layout
Page 43 and 44: 4.2 Interaction Toolbox INTERACTION
Page 53 and 54: 4.3 Specifying the User Interface I
Page 67: 4.3 Specifying the User Interface I
Page 71 and 72: 5.1 Program Architecture IMPLEMENTA
Page 77 and 78: 5.2 An Application of Dynamic Progr
Page 83 and 84: 6 Evaluation EVALUATION In this cha
Page 85 and 86: 6.2 Case Study EVALUATION presented
Page 87 and 88: 6.2 Case Study EVALUATION AÖGHKÖ
Page 89 and 90: 7.2 Résumé CONCLUSION User Studie
Page 91 and 92: References REFERENCES [Adoa] Adobe
Page 93 and 94: REFERENCES [Hur78] A. Hurlburt. The
show all

think-cell technical report TC2003/01 A GUI-based Interaction ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?