Changeset 1043
- Timestamp:
- 10/24/06 00:44:52 (2 years ago)
- Files:
-
- gaphor/branches/new-canvas/doc/items.tex (modified) (6 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
gaphor/branches/new-canvas/doc/items.tex
r1042 r1043 96 96 \section{Introduction} 97 97 UML specification defines UML data model, which is used by Gaphor to store 98 information about modeled system. UML data model is visualized with99 Diacanvas library used as canvaslibrary. Notation100 of UML diagram items is also specified by UML specification.101 102 Diacanvas library supports basic drawing operations but there are many98 information about a modeled system. The UML data model is visualized by 99 the Gaphas library, a general purpose diagram drawing library. Notation 100 of UML diagram items is also specified by the UML specification. 101 102 The Gaphas library supports basic drawing operations but there are many 103 103 entities and behaviors, which are common to many or all diagram items, i.e. 104 stereotypes, item s'name, popup menu, positioning of associated items, etc.104 stereotypes, item name, popup menu, positioning of associated items, etc. 105 105 106 106 We have to identify common elements and behaviors of UML diagram items … … 108 108 by Gaphor to provide modeling functionality. 109 109 110 Note that, the diagram item hierarchy does not have to follow the hierarchy 111 defined in the UML model. 112 110 113 \section{Problem Description} 111 114 … … 118 121 119 122 Because of differences between them, Basic diagram item class cannot be 120 directly associated with canvas line or canvas element. Connection between121 diacanvas classes and items has to be established by different abstract123 directly associated with canvas lines or canvas elements. Connection between 124 canvas classes and items has to be established by different abstract 122 125 classes. 123 126 124 127 \subsection{Items and UML Model Classes} 125 Generaly there is one to one association between an item and UML class126 but it is not always sosimple.128 Generaly there is a one to one association between an item and an UML class, 129 but it is not always that simple. 127 130 For example one diagram item can visualize more than one UML class 128 131 \begin{itemize} … … 132 135 133 136 Also, there can be situation, when there is no UML class visualized, i.e. 134 in case of CommentLine.137 in case of a CommentLine. 135 138 136 139 \subsection{Line Items} 137 Line has at least two handles. These handles are refferedas head (first138 handle) and tail ( secondhandle) of line.139 140 When user puts an item on a diagram, thenlast handle can be moved to141 desired point. The same applies to line items. User putsline on diagram,140 Lines have at least two handles. These handles are reffered to as head (first 141 handle) and tail (last handle) of line. 142 143 When a user puts an item on a diagram, then the last handle can be moved to 144 a desired point. The same applies to line items. User puts a line on diagram, 142 145 head is set in mouse cursor point and tail is moved to desired point. 143 146 144 Head and tail concepts are also used in diacanvas in case of canvas line.147 Head and tail concepts are also used in Gaphas in case of canvas lines. 145 148 Head of line item is at the same end as head of canvas line. The same 146 149 applies for tail. … … 150 153 Many of such parts can be shared by other items, for example 151 154 \begin{itemize} 152 \item UML named elements (see named items) have names, which should be155 \item UML named elements (see named items) have names, which 153 156 can be displayed in different places, i.e. class --- top--center, 154 157 use case --- middle--center … … 280 283 Align constants and classes are defined in \rmodule{gaphor::diagram::align} module. 281 284 282 \subsection{Stereotype and Name Align }285 \subsection{Stereotype and Name Alignment} 283 286 284 287 There are two important elements of items
