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

More documents

Recommendations

Info

5.1 Program Architecture IMPLEMENTATION driven by the document window. 5.1.2 Hierarchy and Interfaces of UI Classes Some selected class diagrams are depicted in figure 38. The root class CUIObject holds a reference to its document window and offers an interface to process all kinds of low level user interface messages. The subclasses realize different UI wid- gets by implementing the processing of those messages differently. In particular, the subclasses of CHotZone offer specific functions that provide a high-level interpretation of the low-level UI input, <strong>based</strong> on notions like hit test, mouse capture and the like. For example, in the case of the CHotButton class, a sequence of the OnLButtonDown()/OnLButtonUp() mouse messages triggers a call to the OnClick() method, if at the times of both events the mouse pointer is found within the UI object’s responsive area. The application specific methods like OnClick() are abstract, meaning that the respective class itself cannot be instantiated. To use the functionality provided by the UI classes, each UI widget is programmed as its own subclass, implementing its specific behavior in those abstract methods. Other UI components are too specific to be derived from CHotZone or its subclasses. Examples are CFeatureOutline and CUIGridLine. These classes implement the interpretation of low-level messages themselves, deriving directly from class CUIObject (Fig. 38(a)). The inheritance graph of CVisualElement (Fig. 38(b)) partly parallels the hierarchy of subclasses of CUIObject. Most UI objects have some visual represen- tation that is made up of one or more visual elements. The methods and attributes of visual elements serve to create an appropriate texture mapping, transforming coordinates from a precompiled texture bitmap to document-oriented coordinates and finally to on-screen coordinates, taking zooming and scrolling into account. The subclasses of CVisualElement are tailored to their specific use with the objective to minimize the interface to their respective subclass of CUIObject. As can be seen in figure 37, features are contained by a smart element and smart elements are contained by a container. Now, figure 38(c)) shows that smart elements also are features and that containers also are smart elements. The class CSmartElement derives from CFeature, because the latter provides functionality to show user interface components, and smart elements need to have a user interface, too. On the other hand, the relationship between CSmartElement and CContainerSE enables hierarchical layouts with gridlines at different levels. 5.1.3 Windows Message Processing User input processing in my prototype is <strong>based</strong> on Microsoft Windows messages. In Windows, messages are responsible for inter-process communication. Messages that originate in the operating system are queued in thread-specific message queues and are processed whenever a thread makes a system call to PeekMessage() or GetMessage(). The user thread then typically makes a call to DispatchMessage(), 72
5.1 Program Architecture IMPLEMENTATION CHotButton +OnClick() C... CVESizedButton #m_rectDoc : _intRect CHotZone #m_ve : CVisualElement #m_bHasMouseCapture : Boolesch CHotDragHandle #m_ptDocAnchor : _intPoint +OnDragStart() +OnDrag() +OnDrop() CGridLineHotDragHandle -m_gridline : CGridLine -m_end : ELineEnd CUIObject #m_pptdocwnd : CPPTDocWnd +OnMouseMove() +OnLButtonDown() +...() +UpdateUI() +Paint() CFeatureOutline #m_cve : Col #m_feature : CFeature CInsertionIndication -m_rectDoc : _intRect (a) UI objects receive and process user input messages from the document window. CVisualElement #m_pptdocwnd : CPPTDocWnd #m_vecptTexture : vector #BuildScreenPoints() : vector +Paint() CVEAnchoredButton #m_ptDocAnchor : _intPoint CVEGridLine #m_orient : EOrientation CVEGridLineHandle #m_end : ELineEnd (b) Visual elements provide visual feedback to explain the state and effect of UI objects. Figure 38: Selected class diagrams 73 CFeature #m_se : CSmartElement #m_bSelected : Boolesch +CreateUI() : Col CSmartElement #m_containerse : CContainerSE +Left() : CGridLine +Top() : CGridLine +Right() : CGridLine +Bottom() : CGridLine CContainerSE #m_smartgrid : CSmartGrid #m_grdlnsX : CGridLineGroup #m_grdlnsY : CGridLineGroup (c) Features represent usermodifiable entities. CUIGridLine -m_gridline : CGridLine
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:
Page 19 and 20:
2.2 Quantitative Aspects FIELD STUD
Page 21 and 22: 2.2 Quantitative Aspects FIELD STUD
Page 23 and 24: 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 69 and 70: 5 Implementation IMPLEMENTATION The
Page 71: 5.1 Program Architecture IMPLEMENTA
Page 75 and 76: 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 ...

Create successful ePaper yourself

Delete template?

Save as template?