Changes for page KIML Layout Options

Last modified by Alexander Schulz-Rosengarten on 2023/09/11 16:17

From version 6.1
edited by cds
on 2013/06/03 10:42
Change comment: There is no comment for this version
To version 23.1
edited by msp
on 2014/03/13 10:36
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.cds
1 +XWiki.msp
Content
... ... @@ -1,24 +1,28 @@
1 -{{warning}}
2 -This is preliminary documentation. You've been warned.
3 -{{/warning}}
1 +
4 4  
5 -KIML defines a whole set of standard layout options that many layout algorithms support. Whether an algorithm supports a layout option depends on the option and on the algorithm. When an option is supported by an algorithm, it may change the option's default value. Algorithms may also provide more specialized documentation for a given layout option.
3 +KIML defines a whole set of standard layout options that many layout algorithms support. When an option is supported by an algorithm, that algorithm may override the option's default value. Algorithms may also provide more specialized documentation for layout options.
6 6  
7 7  **Contents**
8 8  
9 -
10 10  
8 +
9 +{{toc maxLevel="2"/}}
10 +
11 11  = Overview =
12 12  
13 -Beside a human-readable name, layout options are defined by the following properties:
13 +Beside a user-friendly name, layout options are defined by the following properties:
14 14  
15 15  * An ID to identify them.
16 -* A type. One of Boolean, String, Int, Float, Enum, EnumSet (a {{code language="none"}}Set{{/code}} over a given enumeration), or Object. The types Enum and EnumSet have to be further defined by an enumeration class. The Object type can be constricted to a certain class.
17 -* The kinds of graph objects the option applies to. At least one of Parents (nodes that have children, including the diagram root node), Nodes, Edges, Ports, and Labels.
18 -* An optional default value. If an option is not set on an object and if the option does not have a default value, {{code language="none"}}null{{/code}} is returned when it is accessed.
16 +* A type. One of Boolean, String, Int, Float, Enum, EnumSet (a s{{code language="none"}}et{{/code}} over a given enumeration), or Object (a non-primitive Java object). The types Enum and EnumSet have to be further defined by an enumeration class. The Object type can be constricted to a certain Java class.
17 +* The kinds of graph objects the option applies to. At least one of Nodes, Edges, Ports, Labels, or Parents (nodes that have children, including the diagram root node). Parents-applicable options affect whole graphs or subgraphs, while options with other application targets affect only single graph elements.
18 +* An optional default value. A default value may also be provided by the layout algorithm using the option, or by the modeling application you are using. In these cases the value given here is overridden.
19 19  
20 -KIML defines the following set of layout options:
20 +Layout options can be assigned to two main categories: user options and programmatic options.
21 21  
22 +== User Options ==
23 +
24 +User options are those that you can see in the "//Layout View//" available in Eclipse if the KIML user interface is installed. That view is restricted to layout options that are supported by the currently active layout algorithm. Furthermore, some options are visible only when the //Show Advanced Properties// button is active in the view.
25 +
22 22  |=(((
23 23  Option
24 24  )))|=(((
... ... @@ -31,7 +31,7 @@
31 31  Default
32 32  )))
33 33  |(((
34 -Alignment
38 +[[Alignment>>doc:||anchor="alignment"]]
35 35  )))|(((
36 36  de.cau.cs.kieler.alignment
37 37  )))|(((
... ... @@ -42,7 +42,7 @@
42 42  AUTOMATIC
43 43  )))
44 44  |(((
45 -Aspect Ratio
49 +[[Aspect Ratio>>doc:||anchor="aspectRatio"]]
46 46  )))|(((
47 47  de.cau.cs.kieler.aspectRatio
48 48  )))|(((
... ... @@ -72,89 +72,347 @@
72 72  )))|(((
73 73  Parents
74 74  )))|(((
75 --1.0
79 +
76 76  )))
81 +|(((
82 +Debug Mode
83 +)))|(((
84 +de.cau.cs.kieler.debugMode
85 +)))|(((
86 +Boolean
87 +)))|(((
88 +Parents
89 +)))|(((
90 +false
91 +)))
92 +|(((
93 +Direction
94 +)))|(((
95 +de.cau.cs.kieler.direction
96 +)))|(((
97 +Enum
98 +)))|(((
99 +Parents
100 +)))|(((
101 +
102 +)))
103 +|(((
104 +[[Edge Routing>>doc:||anchor="edgeRouting"]]
105 +)))|(((
106 +de.cau.cs.kieler.edgeRouting
107 +)))|(((
108 +Enum
109 +)))|(((
110 +Parents
111 +)))|(((
112 +
113 +)))
114 +|(((
115 +Expand Nodes
116 +)))|(((
117 +de.cau.cs.kieler.expandNodes
118 +)))|(((
119 +Boolean
120 +)))|(((
121 +Parents
122 +)))|(((
123 +false
124 +)))
125 +|(((
126 +Interactive
127 +)))|(((
128 +de.cau.cs.kieler.interactive
129 +)))|(((
130 +Boolean
131 +)))|(((
132 +Parents
133 +)))|(((
134 +false
135 +)))
136 +|(((
137 +Label Spacing
138 +)))|(((
139 +de.cau.cs.kieler.labelSpacing
140 +)))|(((
141 +Float
142 +)))|(((
143 +Edges
144 +Nodes
145 +)))|(((
146 +
147 +)))
148 +|(((
149 +[[Layout Hierarchy>>doc:||anchor="layoutHierarchy"]]
150 +)))|(((
151 +de.cau.cs.kieler.layoutHierarchy
152 +)))|(((
153 +Boolean
154 +)))|(((
155 +Parents
156 +)))|(((
157 +false
158 +)))
159 +|(((
160 +[[Layout Algorithm>>doc:||anchor="layoutAlgorithm"]]
161 +)))|(((
162 +de.cau.cs.kieler.algorithm
163 +)))|(((
164 +String
165 +)))|(((
166 +Parents
167 +)))|(((
168 +
169 +)))
77 77  |(% colspan="1" %)(% colspan="1" %)
78 78  (((
79 -Comment Box
172 +Node Label Placement
80 80  )))|(% colspan="1" %)(% colspan="1" %)
81 81  (((
82 -de.cau.cs.kieler.commentBox
175 +de.cau.cs.kieler.nodeLabelPlacement
83 83  )))|(% colspan="1" %)(% colspan="1" %)
84 84  (((
85 -Boolean
178 +EnumSet
86 86  )))|(% colspan="1" %)(% colspan="1" %)
87 87  (((
88 88  Nodes
89 89  )))|(% colspan="1" %)(% colspan="1" %)
90 90  (((
91 -false
184 +
92 92  )))
93 93  |(((
94 -Debug Mode
187 +Port Constraints
95 95  )))|(((
96 -de.cau.cs.kieler.debugMode
189 +de.cau.cs.kieler.portConstraints
97 97  )))|(((
98 -Boolean
191 +Enum
99 99  )))|(((
100 -Parents
193 +Nodes
101 101  )))|(((
102 -false
195 +
103 103  )))
104 104  |(% colspan="1" %)(% colspan="1" %)
105 105  (((
106 -Diagram Type
199 +Port Label Placement
107 107  )))|(% colspan="1" %)(% colspan="1" %)
108 108  (((
109 -de.cau.cs.kieler.diagramType
202 +de.cau.cs.kieler.portLabelPlacement
110 110  )))|(% colspan="1" %)(% colspan="1" %)
111 111  (((
112 -String
205 +Enum
113 113  )))|(% colspan="1" %)(% colspan="1" %)
114 114  (((
115 -
208 +Nodes
116 116  )))|(% colspan="1" %)(% colspan="1" %)
117 117  (((
211 +OUTSIDE
212 +)))
213 +|(% colspan="1" %)(% colspan="1" %)
214 +(((
215 +Port Spacing
216 +)))|(% colspan="1" %)(% colspan="1" %)
217 +(((
218 +de.cau.cs.kieler.portSpacing
219 +)))|(% colspan="1" %)(% colspan="1" %)
220 +(((
221 +Float
222 +)))|(% colspan="1" %)(% colspan="1" %)
223 +(((
224 +Nodes
225 +)))|(% colspan="1" %)(% colspan="1" %)
226 +(((
118 118  
119 119  )))
120 120  |(((
121 -Direction
230 +Position
122 122  )))|(((
123 -de.cau.cs.kieler.direction
232 +de.cau.cs.kieler.position
124 124  )))|(((
125 -Enum
234 +Object
126 126  )))|(((
127 -Parents
236 +Labels
237 +Nodes
238 +Ports
128 128  )))|(((
129 -UNDEFINED
240 +
130 130  )))
242 +|(((
243 +Priority
244 +)))|(((
245 +de.cau.cs.kieler.priority
246 +)))|(((
247 +Int
248 +)))|(((
249 +Edges
250 +Nodes
251 +)))|(((
252 +
253 +)))
131 131  |(% colspan="1" %)(% colspan="1" %)
132 132  (((
133 -Edge Label Placement
256 +Randomization Seed
134 134  )))|(% colspan="1" %)(% colspan="1" %)
135 135  (((
136 -de.cau.cs.kieler.edgeLabelPlacement
259 +de.cau.cs.kieler.randomSeed
137 137  )))|(% colspan="1" %)(% colspan="1" %)
138 138  (((
139 -Enum
262 +Int
140 140  )))|(% colspan="1" %)(% colspan="1" %)
141 141  (((
142 -Labels
265 +Parents
143 143  )))|(% colspan="1" %)(% colspan="1" %)
144 144  (((
145 -UNDEFINED
268 +
146 146  )))
270 +|(% colspan="1" %)(% colspan="1" %)
271 +(((
272 +Separate Connected Components
273 +)))|(% colspan="1" %)(% colspan="1" %)
274 +(((
275 +de.cau.cs.kieler.separateConnComp
276 +)))|(% colspan="1" %)(% colspan="1" %)
277 +(((
278 +Boolean
279 +)))|(% colspan="1" %)(% colspan="1" %)
280 +(((
281 +Parents
282 +)))|(% colspan="1" %)(% colspan="1" %)
283 +(((
284 +
285 +)))
286 +|(% colspan="1" %)(% colspan="1" %)
287 +(((
288 +Size Constraint
289 +)))|(% colspan="1" %)(% colspan="1" %)
290 +(((
291 +de.cau.cs.kieler.sizeConstraint
292 +)))|(% colspan="1" %)(% colspan="1" %)
293 +(((
294 +EnumSet
295 +)))|(% colspan="1" %)(% colspan="1" %)
296 +(((
297 +Nodes
298 +)))|(% colspan="1" %)(% colspan="1" %)
299 +(((
300 +
301 +)))
302 +|(% colspan="1" %)(% colspan="1" %)
303 +(((
304 +Size Options
305 +)))|(% colspan="1" %)(% colspan="1" %)
306 +(((
307 +de.cau.cs.kieler.sizeOptions
308 +)))|(% colspan="1" %)(% colspan="1" %)
309 +(((
310 +EnumSet
311 +)))|(% colspan="1" %)(% colspan="1" %)
312 +(((
313 +Nodes
314 +)))|(% colspan="1" %)(% colspan="1" %)
315 +(((
316 +DEFAULT_MINIMUM_SIZE
317 +)))
318 +|(% colspan="1" %)(% colspan="1" %)
319 +(((
320 +Spacing
321 +)))|(% colspan="1" %)(% colspan="1" %)
322 +(((
323 +de.cau.cs.kieler.spacing
324 +)))|(% colspan="1" %)(% colspan="1" %)
325 +(((
326 +Float
327 +)))|(% colspan="1" %)(% colspan="1" %)
328 +(((
329 +Parents
330 +)))|(% colspan="1" %)(% colspan="1" %)
331 +(((
332 +
333 +)))
334 +
335 +== Programmatic Options ==
336 +
337 +Programmatic options are such that are meant to be configured exclusively through the KIML API. They should not be visible in the user interface.
338 +
339 +|=(((
340 +Option
341 +)))|=(((
342 +ID
343 +)))|=(((
344 +Type
345 +)))|=(((
346 +Applies to
347 +)))|=(((
348 +Default
349 +)))
350 +|(% colspan="1" %)(% colspan="1" %)
351 +(((
352 +Animate
353 +)))|(% colspan="1" %)(% colspan="1" %)
354 +(((
355 +de.cau.cs.kieler.animate
356 +)))|(% colspan="1" %)(% colspan="1" %)
357 +(((
358 +Boolean
359 +)))|(% colspan="1" %)(% colspan="1" %)
360 +(((
361 +Parents
362 +)))|(% colspan="1" %)(% colspan="1" %)
363 +(((
364 +true
365 +)))
366 +|(% colspan="1" %)(% colspan="1" %)
367 +(((
368 +Animation Time Factor
369 +)))|(% colspan="1" %)(% colspan="1" %)
370 +(((
371 +de.cau.cs.kieler.animTimeFactor
372 +)))|(% colspan="1" %)(% colspan="1" %)
373 +(((
374 +Int
375 +)))|(% colspan="1" %)(% colspan="1" %)
376 +(((
377 +Parents
378 +)))|(% colspan="1" %)(% colspan="1" %)
379 +(((
380 +100
381 +)))
382 +|(% colspan="1" %)(% colspan="1" %)
383 +(((
384 +[[Comment Box>>doc:||anchor="commentBox"]]
385 +)))|(% colspan="1" %)(% colspan="1" %)
386 +(((
387 +de.cau.cs.kieler.commentBox
388 +)))|(% colspan="1" %)(% colspan="1" %)
389 +(((
390 +Boolean
391 +)))|(% colspan="1" %)(% colspan="1" %)
392 +(((
393 +Nodes
394 +)))|(% colspan="1" %)(% colspan="1" %)
395 +(((
396 +false
397 +)))
147 147  |(((
148 -Edge Routing
399 +[[Diagram Type>>doc:||anchor="diagramType"]]
149 149  )))|(((
150 -de.cau.cs.kieler.edgeRouting
401 +de.cau.cs.kieler.diagramType
151 151  )))|(((
152 -Enum
403 +String
153 153  )))|(((
154 154  Parents
155 155  )))|(((
156 -UNDEFINED
407 +
157 157  )))
409 +|(((
410 +Edge Label Placement
411 +)))|(((
412 +de.cau.cs.kieler.edgeLabelPlacement
413 +)))|(((
414 +Enum
415 +)))|(((
416 +Labels
417 +)))|(((
418 +
419 +)))
158 158  |(% colspan="1" %)(% colspan="1" %)
159 159  (((
160 160  Edge Type
... ... @@ -171,17 +171,6 @@
171 171  (((
172 172  NONE
173 173  )))
174 -|(((
175 -Expand Nodes
176 -)))|(((
177 -de.cau.cs.kieler.expandNodes
178 -)))|(((
179 -Boolean
180 -)))|(((
181 -Parents
182 -)))|(((
183 -false
184 -)))
185 185  |(% colspan="1" %)(% colspan="1" %)
186 186  (((
187 187  Font Name
... ... @@ -216,7 +216,7 @@
216 216  )))
217 217  |(% colspan="1" %)(% colspan="1" %)
218 218  (((
219 -Hypernode
470 +[[Hypernode>>doc:||anchor="hypernode"]]
220 220  )))|(% colspan="1" %)(% colspan="1" %)
221 221  (((
222 222  de.cau.cs.kieler.hypernode
... ... @@ -230,50 +230,53 @@
230 230  (((
231 231  false
232 232  )))
233 -|(((
234 -Interactive
235 -)))|(((
236 -de.cau.cs.kieler.interactive
237 -)))|(((
484 +|(% colspan="1" %)(% colspan="1" %)
485 +(((
486 +Layout Ancestors
487 +)))|(% colspan="1" %)(% colspan="1" %)
488 +(((
489 +de.cau.cs.kieler.layoutAncestors
490 +)))|(% colspan="1" %)(% colspan="1" %)
491 +(((
238 238  Boolean
239 -)))|(((
493 +)))|(% colspan="1" %)(% colspan="1" %)
494 +(((
240 240  Parents
241 -)))|(((
496 +)))|(% colspan="1" %)(% colspan="1" %)
497 +(((
242 242  false
243 243  )))
244 -|(((
245 -Label Spacing
246 -)))|(((
247 -de.cau.cs.kieler.labelSpacing
248 -)))|(((
249 -Float
250 -)))|(((
251 -Edges
252 -Nodes
253 -)))|(((
254 --1.0
255 -)))
256 -|(((
257 -Layout Hierarchy
258 -)))|(((
259 -de.cau.cs.kieler.layoutHierarchy
260 -)))|(((
261 -Boolean
262 -)))|(((
500 +|(% colspan="1" %)(% colspan="1" %)
501 +(((
502 +Maximal Animation Time
503 +)))|(% colspan="1" %)(% colspan="1" %)
504 +(((
505 +de.cau.cs.kieler.maxAnimTim
506 +)))|(% colspan="1" %)(% colspan="1" %)
507 +(((
508 +Int
509 +)))|(% colspan="1" %)(% colspan="1" %)
510 +(((
263 263  Parents
264 -)))|(((
265 -false
512 +)))|(% colspan="1" %)(% colspan="1" %)
513 +(((
514 +4000
266 266  )))
267 -|(((
268 -Layout Algorithm
269 -)))|(((
270 -de.cau.cs.kieler.algorithm
271 -)))|(((
272 -String
273 -)))|(((
516 +|(% colspan="1" %)(% colspan="1" %)
517 +(((
518 +Minimal Animation Time
519 +)))|(% colspan="1" %)(% colspan="1" %)
520 +(((
521 +de.cau.cs.kieler.minAnimTim
522 +)))|(% colspan="1" %)(% colspan="1" %)
523 +(((
524 +Int
525 +)))|(% colspan="1" %)(% colspan="1" %)
526 +(((
274 274  Parents
275 -)))|(((
276 -
528 +)))|(% colspan="1" %)(% colspan="1" %)
529 +(((
530 +400
277 277  )))
278 278  |(% colspan="1" %)(% colspan="1" %)
279 279  (((
... ... @@ -311,7 +311,7 @@
311 311  )))
312 312  |(% colspan="1" %)(% colspan="1" %)
313 313  (((
314 -No Layout
568 +[[No Layout>>doc:||anchor="noLayout"]]
315 315  )))|(% colspan="1" %)(% colspan="1" %)
316 316  (((
317 317  de.cau.cs.kieler.noLayout
... ... @@ -327,49 +327,22 @@
327 327  )))
328 328  |(% colspan="1" %)(% colspan="1" %)
329 329  (((
330 -Node Label Placement
584 +Port Index
331 331  )))|(% colspan="1" %)(% colspan="1" %)
332 332  (((
333 -de.cau.cs.kieler.nodeLabelPlacement
587 +de.cau.cs.kieler.portIndex
334 334  )))|(% colspan="1" %)(% colspan="1" %)
335 335  (((
336 -EnumSet
590 +Int
337 337  )))|(% colspan="1" %)(% colspan="1" %)
338 338  (((
339 -Nodes
593 +Ports
340 340  )))|(% colspan="1" %)(% colspan="1" %)
341 341  (((
342 342  
343 343  )))
344 -|(((
345 -Port Constraints
346 -)))|(((
347 -de.cau.cs.kieler.portConstraints
348 -)))|(((
349 -Enum
350 -)))|(((
351 -Nodes
352 -)))|(((
353 -UNDEFINED
354 -)))
355 355  |(% colspan="1" %)(% colspan="1" %)
356 356  (((
357 -Port Label Placement
358 -)))|(% colspan="1" %)(% colspan="1" %)
359 -(((
360 -de.cau.cs.kieler.portLabelPlacement
361 -)))|(% colspan="1" %)(% colspan="1" %)
362 -(((
363 -Enum
364 -)))|(% colspan="1" %)(% colspan="1" %)
365 -(((
366 -Nodes
367 -)))|(% colspan="1" %)(% colspan="1" %)
368 -(((
369 -OUTSIDE
370 -)))
371 -|(% colspan="1" %)(% colspan="1" %)
372 -(((
373 373  [[Port Offset>>doc:||anchor="portOffset"]]
374 374  )))|(% colspan="1" %)(% colspan="1" %)
375 375  (((
... ... @@ -398,57 +398,16 @@
398 398  Ports
399 399  )))|(% colspan="1" %)(% colspan="1" %)
400 400  (((
401 -UNDEFINED
402 -)))
403 -|(((
404 -Position
405 -)))|(((
406 -de.cau.cs.kieler.position
407 -)))|(((
408 -Object
409 -)))|(((
410 -Labels
411 -Nodes
412 -Ports
413 -)))|(((
414 414  
415 415  )))
416 -|(((
417 -Priority
418 -)))|(((
419 -de.cau.cs.kieler.priority
420 -)))|(((
421 -Int
422 -)))|(((
423 -Edges
424 -Nodes
425 -)))|(((
426 -
427 -)))
428 428  |(% colspan="1" %)(% colspan="1" %)
429 429  (((
430 -Randomization Seed
632 +Progress Bar
431 431  )))|(% colspan="1" %)(% colspan="1" %)
432 432  (((
433 -de.cau.cs.kieler.randomSeed
635 +de.cau.cs.kieler.progressBar
434 434  )))|(% colspan="1" %)(% colspan="1" %)
435 435  (((
436 -Int
437 -)))|(% colspan="1" %)(% colspan="1" %)
438 -(((
439 -Parents
440 -)))|(% colspan="1" %)(% colspan="1" %)
441 -(((
442 -
443 -)))
444 -|(% colspan="1" %)(% colspan="1" %)
445 -(((
446 -Separate Connected Components
447 -)))|(% colspan="1" %)(% colspan="1" %)
448 -(((
449 -de.cau.cs.kieler.separateConnComp
450 -)))|(% colspan="1" %)(% colspan="1" %)
451 -(((
452 452  Boolean
453 453  )))|(% colspan="1" %)(% colspan="1" %)
454 454  (((
... ... @@ -455,67 +455,214 @@
455 455  Parents
456 456  )))|(% colspan="1" %)(% colspan="1" %)
457 457  (((
458 -
644 +false
459 459  )))
460 460  |(% colspan="1" %)(% colspan="1" %)
461 461  (((
462 -Size Constraint
648 +Scale Factor
463 463  )))|(% colspan="1" %)(% colspan="1" %)
464 464  (((
465 -de.cau.cs.kieler.sizeConstraint
651 +de.cau.cs.kieler.scaleFactor
466 466  )))|(% colspan="1" %)(% colspan="1" %)
467 467  (((
468 -EnumSet
654 +Float
469 469  )))|(% colspan="1" %)(% colspan="1" %)
470 470  (((
471 471  Nodes
472 472  )))|(% colspan="1" %)(% colspan="1" %)
473 473  (((
474 -
660 +1.0
475 475  )))
476 476  |(% colspan="1" %)(% colspan="1" %)
477 477  (((
478 -Size Options
664 +Thickness
479 479  )))|(% colspan="1" %)(% colspan="1" %)
480 480  (((
481 -de.cau.cs.kieler.sizeOptions
667 +de.cau.cs.kieler.thickness
482 482  )))|(% colspan="1" %)(% colspan="1" %)
483 483  (((
484 -EnumSet
670 +Float
485 485  )))|(% colspan="1" %)(% colspan="1" %)
486 486  (((
487 -Nodes
673 +Edges
488 488  )))|(% colspan="1" %)(% colspan="1" %)
489 489  (((
490 -DEFAULT_MINIMUM_SIZE
676 +1.0
491 491  )))
492 492  |(% colspan="1" %)(% colspan="1" %)
493 493  (((
494 -Spacing
680 +Zoom to Fit
495 495  )))|(% colspan="1" %)(% colspan="1" %)
496 496  (((
497 -de.cau.cs.kieler.spacing
683 +de.cau.cs.kieler.zoomToFit
498 498  )))|(% colspan="1" %)(% colspan="1" %)
499 499  (((
500 -Float
686 +Boolean
501 501  )))|(% colspan="1" %)(% colspan="1" %)
502 502  (((
503 503  Parents
504 504  )))|(% colspan="1" %)(% colspan="1" %)
505 505  (((
506 --1.0
692 +false
507 507  )))
508 508  
509 -= The Most Important Options =
695 +=== Layout Output Properties ===
510 510  
511 -**TODO:** Write a bit of documentation about the most important layout options and how to use them, possibly with a simple example or something.
697 +A few properties are used as additional information in the output of a layout algorithm. This information should be considered when the layout is applied to the original diagram
512 512  
699 +|=(((
700 +Property
701 +)))|=(((
702 +ID
703 +)))|=(((
704 +Type
705 +)))|=(((
706 +Applies to
707 +)))
708 +|(((
709 +[[Edge Routing>>doc:||anchor="edgeRouting"]]
710 +)))|(((
711 +de.cau.cs.kieler.edgeRouting
712 +)))|(((
713 +Enum
714 +)))|(((
715 +Edges
716 +)))
717 +|(((
718 +Junction Points
719 +)))|(((
720 +de.cau.cs.kieler.junctionPoints
721 +)))|(((
722 +Object
723 +)))|(((
724 +Edges
725 +)))
726 +
727 +
728 +
513 513  = Detailed Documentation =
514 514  
515 515  This section explains every layout option in more detail.
516 516  
517 -== Port Offset ==
733 +== The Most Important Options ==
518 518  
735 +While most layout options are used to affect how the active layout algorithm computes concrete coordinates for the graph elements, there are some layout options that have a special role in KIML.
736 +
737 +=== Layout Algorithm ===
738 +
739 +{{id name="layoutAlgorithm"/}}
740 +
741 +The option with identifier {{code language="none"}}de.cau.cs.kieler.algorithm{{/code}} specifies which layout algorithm to use for a graph or subgraph. The value can be either the identifier of a layout algorithm or the identifier of a layout type. In the latter case the algorithm with highest priority of that type is applied. It is possible to set different values for this option on subgraphs of a hierarchical graph, where a subgraph is identified by a parent node. A layout algorithm is responsible to process only the direct content of a given parent node. An exception from this rule is made when the [[Layout Hierarchy>>doc:||anchor="layoutHierarchy"]] option is active.
742 +
743 +The following layout has been created by setting a force-based layout algorithm on the inner hierarchy level and a layer-based layout algorithm on the top level.
744 +
745 +[[image:attach:layout_algorithm.png]]
746 +
747 +==== Available Algorithms and Libraries ====
748 +
749 +* **The [[KLay Project>>doc:Layout Algorithms (KLay)]]** - Java implementations of standard layout approaches, augmented with special processing of graph features such as ports and labels.
750 +* **Randomizer** - Distributes the nodes randomly; not very useful, but it can show how important a good layout is for understanding a graph.
751 +* (((
752 +**Box Layout** - Ignores edges, places all nodes in rows. Can be used to layout collections of unconnected boxes, such as Statechart regions.
753 +)))
754 +* **Fixed Layout** - Does not compute a new layout, but leaves all nodes and edges where they are. If the Position and Bend Points options are set for the elements of the graph, the pre-defined layout is applied.
755 +* **OGDF** ((% style="color: rgb(0,0,0);" %)[[www.ogdf.net>>url:http://www.ogdf.net/||shape="rect"]](%%)) - A self-contained C++ class library for the automatic layout of diagrams. The version that is shipped with KIELER is compiled as an executable that reads files in OGML format and outputs the computed concrete layout.
756 +* **Graphviz** ([[www.graphviz.org>>url:http://www.graphviz.org/||shape="rect"]]) - An open source graph visualization tool with several graph layout programs, web and interactive graphical interfaces, auxiliary tools, libraries, and language bindings. Graphviz needs to be installed separately in order to be used within KIELER, since it is called in a separate process using the DOT language for communication.
757 +
758 +==== Predefined Layout Types ====
759 +
760 +* **Layered** - The layer-based method emphasizes the direction of edges by pointing as many edges as possible into the same direction. The nodes are arranged in layers and then reordered such that the number of edge crossings is minimized. Afterwards, concrete coordinates are computed for the nodes and edge bend points.
761 +* **Orthogonal** - Orthogonal methods follow the "topology-shape-metrics" approach, which first applies a planarization technique, resulting in a planar representation of the graph, then compute an orthogonal shape, and finally determine concrete coordinates for nodes and edge bend points by applying a compaction method.
762 +* **Force** - Layout algorithms that follow physical analogies by simulating a system of attractive and repulsive forces.
763 +* **Circular** - Circular layout algorithms emphasize biconnected components of a graph by arranging them in circles. This is useful if a drawing is desired where such components are clearly grouped, or where cycles are shown as prominent properties of the graph.
764 +* **Tree** - Specialized layout methods for trees, i.e. acyclic graphs. The regular structure of graphs that have no undirected cycles can be emphasized using an algorithm of this type.
765 +
766 +=== Diagram Type ===
767 +
768 +{{id name="diagramType"/}}
769 +
770 +Diagram types are used to classify graphical diagrams for setting default layout option values for a set of similar diagrams. The diagram type of an element is specified with the layout option {{code language="none"}}de.cau.cs.kieler.diagramType{{/code}}. Layout algorithms can declare which diagram types they support well, and give a priority value for each supported type. KIML decides at runtime which layout algorithm has the highest priority for a given diagram, so that the most suitable algorithm is always used. Usual values for such priorities are between 1 and 10, where the highest value should only be assigned if the algorithm is especially designed for diagrams of the respective type, or if it has proven to be very adequate for them. Lower values should be given if the algorithm is able to draw the diagrams correctly, but with lower quality of the resulting layout.
771 +
772 +The following diagram types are predefined:
773 +
774 +* **General** - This type is automatically assigned to all diagrams for which no specific type is declared. A layout algorithm that has the highest priority on the //General// diagram type is taken as the default algorithm when no further information on a diagram is available to KIML.
775 +* **State Machine** - All kinds of state machines, automata, and activity diagrams. Examples: [[doc:SCCharts SyncCharts]], UML Activity diagrams.
776 +* **Data Flow Diagram** - Actor-oriented diagrams, where connections are mostly done between //ports// of nodes. These diagrams can only be handled properly by very special layout algorithms, such as those developed in the [[KLay project>>doc:Layout Algorithms (KLay)]].
777 +* **Class Diagram** - Class diagrams such as Ecore diagrams for the [[EMF>>url:http://www.eclipse.org/modeling/emf/||shape="rect"]] or UML Class diagrams.
778 +* **Use Case Diagram** - Use case diagrams as defined by the UML.
779 +* **Unconnected Boxes** - Sets of nodes that have no connections and are treated as resizable boxes. This is related to mathematical [[packing problems>>url:http://en.wikipedia.org/wiki/Packing_problem||shape="rect"]]. Example: Regions in [[doc:SCCharts SyncCharts]].
780 +
781 +=== Edge Routing ===
782 +
783 +{{id name="edgeRouting"/}}
784 +
785 +This option influences the way in which edges are routed between the nodes they connect. The following settings are available:
786 +
787 +* POLYLINE
788 +Edges consist of one or more segments defined by a list of bend points.
789 +* ORTHOGONAL
790 +Edges are routed orthogonally, meaning that each segment of an edge runs either horizontally or vertically.
791 +* SPLINES
792 +Edges are routed as splines (smooth curves).
793 +* UNDEFINED
794 +No particular edge routing style is selected. Usually this value points to the default setting of the selected layout algorithm.
795 +
796 +[[image:attach:edge_routing.png]]
797 +
798 +When used as layout option, the edge routing is set for a whole graph or subgraph, i.e. on a parent node. However, the property is additionally used for the output of the layout algorithm in order to mark individual edges. If the edge routing assigned to an edge is anything other than SPLINES, the bend points of that edge are interpreted with their normal meaning, i.e. straight lines are drawn between consecutive bend points. If, on the other hand, a layout algorithm marks an edge with the value SPLINES, the bend points have to be interpreted as control points for a series of cubic splines following this procedure:
799 +
800 +1. Start at the source point of the edge.
801 +1. As long as there are at least three bend points left:
802 +11. Draw a cubic spline segment to the third bend point with the other two bend points as control points.
803 +11. Use the third bend point as start point for the next segment.
804 +11. Consume the three bend points and proceed to the next segment.
805 +1. Check the number of remaining bend points:
806 +11. Two bend points – draw a cubic spline segment to the target point of the edge.
807 +11. One bend point – draw a quadratic spline segment to the target point of the edge.
808 +11. No bend point – draw a straight line to the target point of the edge.
809 +
810 +== Other Options ==
811 +
812 +=== Alignment ===
813 +
814 +{{id name="alignment"/}}
815 +
816 +Determines the alignment of a node in relation to other nodes of the same row or column. For layer-based algorithms, for instance, this option controls how a node is positioned inside its assigned layer.
817 +
818 +=== Aspect Ratio ===
819 +
820 +{{id name="aspectRatio"/}}
821 +
822 +The aspect ratio of a drawing is the ratio of its total width to its total height. This option gives some control over that ratio, although in most cases it is only interpreted as a hint on how to arrange multiple connected components, hence the actual aspect ratio will probably be different from what has been specified with the option.
823 +
824 +=== Comment Box ===
825 +
826 +{{id name="commentBox"/}}
827 +
828 +A node that is marked as comment box is treated as a label that needs to be placed somewhere. In contrast to normal node labels (modeled with a KLabel instance), comment boxes may have connections to other nodes, as in the following example.
829 +
830 +[[image:attach:comment_box.png]]
831 +
832 +=== (% style="line-height: 1.5625;" %)Hypernode(%%) ===
833 +
834 +{{id name="hypernode"/}}
835 +
836 +A node that is marked as hypernode has a special role in the graph structure, since all its incident edges are treated as parts of the same [[hyperedge>>url:http://en.wikipedia.org/wiki/Hypergraph||shape="rect"]]. Example: relation vertices in [[Ptolemy>>url:http://ptolemy.eecs.berkeley.edu/||shape="rect"]] models.
837 +
838 +=== Layout Hierarchy ===
839 +
840 +{{id name="layoutHierarchy"/}}
841 +
842 +If this option is supported and active, the layout algorithm is requested to process the full hierarchy contained in the input node. This means that instead of executing another algorithm on each hierarchy level, all levels are arranged in a single algorithm execution.
843 +
844 +=== No Layout ===
845 +
846 +{{id name="noLayout"/}}
847 +
848 +Elements that are marked with this option are excluded from layout. This is used to identify diagram objects that should not be regarded as graph elements.
849 +
850 +=== Port Offset ===
851 +
519 519  {{id name="portOffset"/}}
520 520  
521 521  The port offset is used to specify how much space a layout algorithm should leave between a port and the border of its node. This is usually zero, but doesn't have to be. If the offset is not defined for a given port, a layout algorithm can try to infer the offset from the port's coordinates and its node's size in the input graph. This of course requires both properties to be set to sensible values.
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -7111110
1 +9470042
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/7111110/KIML Layout Options
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/9470042/KIML Layout Options