Last modified by Alexander Schulz-Rosengarten on 2023/07/11 10:33
<
From version < 17.1 >
edited by msp
on 2014/03/06 11:11
To version < 19.1 >
edited by msp
on 2014/03/06 13:43
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -36,7 +36,7 @@
36 36  </extension>
37 37  {{/code}}
38 38  
39 -(% style="line-height: 1.4285715;" %)Let's walk through the attributes available for layout options (not every available attribute appears in the example above):
39 +(% style="line-height: 1.4285715;" %)Such declarations are provided by layout algorithm developers, but not by tool developers who merely want to connect the layout infrastructure to their diagram viewers. Let's walk through the attributes available for layout options (not every available attribute appears in the example above):
40 40  
41 41  * (% style="line-height: 1.4285715;" %){{code language="none"}}id{{/code}} – A unique identifier for this layout option. It is recommended that the identifier be prefixed by the plug-in name, to guarantee uniqueness.(%%)\\
42 42  * {{code language="none"}}type{{/code}} – Defines the data type of this option; must be either {{code language="none"}}boolean{{/code}}, {{code language="none"}}string{{/code}}, {{code language="none"}}int{{/code}}, {{code language="none"}}float{{/code}}, {{code language="none"}}enum{{/code}}, {{code language="none"}}enumset{{/code}}, or {{code language="none"}}object{{/code}}. The types {{code language="none"}}enum{{/code}}, {{code language="none"}}enumset{{/code}}, and {{code language="none"}}object{{/code}} require the {{code language="none"}}class{{/code}} attribute to be set.
... ... @@ -74,7 +74,7 @@
74 74  
75 75  = (% style="line-height: 1.4285715;" %)The Layout Option Manager(%%) =
76 76  
77 -(% style="line-height: 1.4285715;" %)By now, we have an idea of what layout options do and why they are important in the first place. However, we haven't looked at how layout options end up on [[KGraph>>doc:KGraph Meta Model]] elements yet. This is where the [[{{code language="none"}}LayoutOptionManager{{/code}}>>url:http://git.rtsys.informatik.uni-kiel.de/projects/KIELER/repos/pragmatics/browse/plugins/de.cau.cs.kieler.kiml.service/src/de/cau/cs/kieler/kiml/service/LayoutOptionManager.java||shape="rect"]] comes in.
77 +(% style="line-height: 1.4285715;" %)By now, we have an idea of what layout options do and why they are important in the first place. However, we haven't looked at how layout options end up on [[KGraph>>doc:KGraph Meta Model]] elements yet. This is where the [[{{code language="none"}}LayoutOptionManager{{/code}}>>url:http://git.rtsys.informatik.uni-kiel.de/projects/KIELER/repos/pragmatics/browse/plugins/de.cau.cs.kieler.kiml.service/src/de/cau/cs/kieler/kiml/service/LayoutOptionManager.java||shape="rect"]] comes in. If you are not interested in the internal details, but want to configure automatic layout for your diagram viewer or editor, you may skip this section and proceed to [[programmatically setting layout options>>doc:||anchor="programmatic-config"]].
78 78  
79 79  (% style="line-height: 1.4285715;" %)After a diagram layout manager has finished turning a given diagram into its KGraph representation, the layout option manager is asked to enrich the KGraph elements with layout options. The option values can come from different sources: the user might have set some using the layout view; there might be some defaults for certain kinds of diagrams; or the programmer might have decided to attach some layout options to certain elements for just this one layout run. Whatever the source, the options manager is in charge of collecting all these layout option values and making sure they find their way to the correct KGraph element. To start off with a clean plate, it first makes sure there are no layout options attached to the KGraph elements. It then does two things: collect every eligible source of layout options, and transfer values of layout options to the associated KGraph elements. Sounds easy enough.
80 80  
... ... @@ -109,6 +109,8 @@
109 109  
110 110  = (% style="line-height: 1.4285715;" %)Programmatically Setting Layout Options(%%) =
111 111  
112 +{{id name="programmatic-config"/}}
113 +
112 112  (% style="line-height: 1.4285715;" %)So with all these layout configurators available, how do you actually go about setting values for layout options programmatically? Well, as always: it depends.
113 113  
114 114  == (% style="line-height: 1.4285715;" %)Using the Extension Point(%%) ==
... ... @@ -129,6 +129,70 @@
129 129  
130 130  (% style="line-height: 1.4285715;" %)Here {{code language="none"}}class{{/code}} refers to a domain model class, in this case the {{code language="none"}}EReference{{/code}} class from the Ecore meta model defined by EMF, and {{code language="none"}}option{{/code}} refers to a layout option through its identifier. The meaning of this declaration is that whenever automatic layout is requested for an Ecore class diagram, the {{code language="none"}}edgeType{{/code}} option is set to {{code language="none"}}ASSOCIATION{{/code}}(%%) for all edges linked to instances of {{code language="none"}}EReference{{/code}}. Since the domain model (//abstract syntax//) is independent of the specific diagram viewer (//concrete syntax//), this configuration is applied to all diagram viewers that use the Ecore meta model.
131 131  
132 -
134 +Alternatively to domain model elements, {{code language="none"}}staticConfig{{/code}} may also reference concrete syntax elements:
133 133  
134 -(% style="line-height: 1.4285715;" %)
136 +{{code language="xml"}}
137 + <staticConfig
138 + class="org.eclipse.emf.ecoretools.diagram.edit.parts.EClassESuperTypesEditPart"
139 + option="de.cau.cs.kieler.edgeType"
140 + value="GENERALIZATION">
141 + </staticConfig>
142 +{{/code}}
143 +
144 +This layout option value is applied only to edges linked to instances of {{code language="none"}}EClassESuperTypesEditPart{{/code}}, which is a concrete syntax element of the Ecore Tools class diagram editor. Other Ecore meta model editors are not affected by this declaration. This distinction is particularly useful for meta models that are accessed with multiple different editors, as is often the case for UML tools.
145 +
146 +A third variant is the use of //diagram types//, as in this example:
147 +
148 +{{code language="xml"}}
149 + <diagramType
150 + id="de.cau.cs.kieler.layout.diagrams.classDiagram"
151 + name="Class Diagram">
152 + </diagramType>
153 + <staticConfig
154 + class="org.eclipse.emf.ecore.EPackage"
155 + option="de.cau.cs.kieler.diagramType"
156 + value="de.cau.cs.kieler.layout.diagrams.classDiagram">
157 + </staticConfig>
158 + <staticConfig
159 + class="de.cau.cs.kieler.layout.diagrams.classDiagram"
160 + option="de.cau.cs.kieler.edgeRouting"
161 + value="SPLINES">
162 + </staticConfig>
163 +{{/code}}
164 +
165 +A diagram type can be declared with a {{code language="none"}}diagramType{{/code}} element and can be associated with an abstract syntax or concrete syntax class using the {{code language="none"}}diagramType{{/code}} option, as shown in the first {{code language="none"}}staticConfig{{/code}} declaration in the example above. The second {{code language="none"}}staticConfig{{/code}} sets an option for the declared diagram type by using its identifier in the {{code language="none"}}class{{/code}} attribute. This kind of indirection is very useful when you have //n// model classes and you want to set //m// layout options for each of those classes. Instead of writing //n// × //m// static declarations, you assign a diagram type //t// to each of the //n// classes and then declare the //m// layout options for //t//, resulting in //n// + //m// option declarations (in many cases //n// + //m// < //n// × //m//).
166 +
167 +A further use of diagram types is for the selection of layout algorithms: a layout algorithm may declare that is is especially suited to process diagrams of certain type //t//. If the diagram type //t// is assigned to a diagram viewer, the most suitable layout algorithm is chosen automatically for that viewer.
168 +
169 +=== semanticConfig ===
170 +
171 +A {{code language="none"}}semanticConfig{{/code}} element registers a subclass of [[SemanticLayoutConfig>>url:https://git.rtsys.informatik.uni-kiel.de/projects/KIELER/repos/pragmatics/browse/plugins/de.cau.cs.kieler.kiml/src/de/cau/cs/kieler/kiml/config/SemanticLayoutConfig.java||shape="rect"]]:
172 +
173 +{{code language="xml"}}
174 + <semanticOption
175 + class="de.cau.cs.kieler.synccharts.Scope"
176 + config="de.cau.cs.kieler.synccharts.diagram.custom.AnnotationsLayoutConfig">
177 + </semanticOption>
178 +{{/code}}
179 +
180 +Similarly to {{code language="none"}}staticConfig{{/code}} entries, the {{code language="none"}}class{{/code}} attribute refers to which model elements the configuration is applied. However, only domain model (a.k.a. //semantic// model) classes may be referenced. The {{code language="none"}}config{{/code}} attribute names a concrete implementation of the semantic layout configurator.
181 +
182 +The advantage of this kind of configuration compared to {{code language="none"}}staticConfig{{/code}} declarations is that it may perform arbitrary analyses of the domain model. For instance, different option values may be computed depending on certain properties of the domain model elements. This approach can be used to enable annotations of domain model elements. When the domain model is stored with a textual format, e.g. defined with [[Xtext>>url:http://www.eclipse.org/Xtext/||shape="rect"]], such annotations can be written in the source file that specifies the model:
183 +
184 +{{code}}
185 +@portConstraints FIXED_SIDE
186 +@minWidth 20.0
187 +@minHeight 15.0
188 +entity IdentityActor
189 +{
190 + @portSide WEST
191 + port Input;
192 +
193 + @portSide EAST
194 + port Output;
195 +}
196 +{{/code}}
197 +
198 +The source file annotations can be translated to KIML layout options with a semantic layout configurator, which is registered to each domain model class where annotations can occur.
199 +
200 +
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -9469988
1 +9469995
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/9469988/Configuring Automatic Layout
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/9469995/Configuring Automatic Layout

Navigation

Quick Links

KIELER on GitHub
RTSYS Homepage