Changes for page KIML Layout Options
on 2014/04/15 10:44
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,26 +1,28 @@ 1 -{{warning}} 2 -This is preliminary and incomplete 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. Whe theranalgorithmsupports a layout option dependsonthe optionandon thealgorithm.Whenan optionis supported byan algorithm,itmaychange the option's default value. Algorithms may also provide more specialized documentation fora givenlayout 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 9 10 10 11 -{{toc/}} 9 +{{toc maxLevel="2"/}} 12 12 13 13 = Overview = 14 14 15 -Beside a human-readablename, layout options are defined by the following properties:13 +Beside a user-friendly name, layout options are defined by the following properties: 16 16 17 17 * An ID to identify them. 18 -* 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.19 -* 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,andLabels.20 -* An optional default value. If anoptionisnotset onanobjectandifthe optiondoesnothaveadefaultvalue, {{code language="none"}}null{{/code}}isreturnedwhenitisaccessed.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. 21 21 22 - KIMLdefinesthefollowing setoflayout options:20 +Layout options can be assigned to two main categories: user options and programmatic options. 23 23 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 + 24 24 |=((( 25 25 Option 26 26 )))|=((( ... ... @@ -33,7 +33,7 @@ 33 33 Default 34 34 ))) 35 35 |((( 36 -Alignment 38 +[[Alignment>>doc:||anchor="alignment"]] 37 37 )))|((( 38 38 de.cau.cs.kieler.alignment 39 39 )))|((( ... ... @@ -44,7 +44,7 @@ 44 44 AUTOMATIC 45 45 ))) 46 46 |((( 47 -Aspect Ratio 49 +[[Aspect Ratio>>doc:||anchor="aspectRatio"]] 48 48 )))|((( 49 49 de.cau.cs.kieler.aspectRatio 50 50 )))|((( ... ... @@ -74,89 +74,363 @@ 74 74 )))|((( 75 75 Parents 76 76 )))|((( 77 - -1.079 + 78 78 ))) 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 +))) 79 79 |(% colspan="1" %)(% colspan="1" %) 80 80 ((( 81 - CommentBox172 +Node Label Placement 82 82 )))|(% colspan="1" %)(% colspan="1" %) 83 83 ((( 84 -de.cau.cs.kieler. commentBox175 +de.cau.cs.kieler.nodeLabelPlacement 85 85 )))|(% colspan="1" %)(% colspan="1" %) 86 86 ((( 87 - Boolean178 +EnumSet 88 88 )))|(% colspan="1" %)(% colspan="1" %) 89 89 ((( 90 90 Nodes 91 91 )))|(% colspan="1" %)(% colspan="1" %) 92 92 ((( 93 - false184 + 94 94 ))) 95 95 |((( 96 - DebugMode187 +Port Constraints 97 97 )))|((( 98 -de.cau.cs.kieler. debugMode189 +de.cau.cs.kieler.portConstraints 99 99 )))|((( 100 - Boolean191 +Enum 101 101 )))|((( 102 - Parents193 +Nodes 103 103 )))|((( 104 - false195 + 105 105 ))) 106 106 |(% colspan="1" %)(% colspan="1" %) 107 107 ((( 108 - DiagramType199 +Port Label Placement 109 109 )))|(% colspan="1" %)(% colspan="1" %) 110 110 ((( 111 -de.cau.cs.kieler. diagramType202 +de.cau.cs.kieler.portLabelPlacement 112 112 )))|(% colspan="1" %)(% colspan="1" %) 113 113 ((( 114 - String205 +Enum 115 115 )))|(% colspan="1" %)(% colspan="1" %) 116 116 ((( 117 - 208 +Nodes 118 118 )))|(% colspan="1" %)(% colspan="1" %) 119 119 ((( 211 +OUTSIDE 212 +))) 213 +|(% colspan="1" %)(% colspan="1" %) 214 +((( 215 + 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 +((( 120 120 121 121 ))) 122 122 |((( 123 - Direction230 +Position 124 124 )))|((( 125 -de.cau.cs.kieler. direction232 +de.cau.cs.kieler.position 126 126 )))|((( 127 - Enum234 +Object 128 128 )))|((( 129 -Parents 236 +Labels 237 +Nodes 238 +Ports 130 130 )))|((( 131 - UNDEFINED240 + 132 132 ))) 242 +|((( 243 +Priority 244 +)))|((( 245 +de.cau.cs.kieler.priority 246 +)))|((( 247 +Int 248 +)))|((( 249 +Edges 250 +Nodes 251 +)))|((( 252 + 253 +))) 133 133 |(% colspan="1" %)(% colspan="1" %) 134 134 ((( 135 - Edge LabelPlacement256 +Randomization Seed 136 136 )))|(% colspan="1" %)(% colspan="1" %) 137 137 ((( 138 -de.cau.cs.kieler. edgeLabelPlacement259 +de.cau.cs.kieler.randomSeed 139 139 )))|(% colspan="1" %)(% colspan="1" %) 140 140 ((( 141 - Enum262 +Int 142 142 )))|(% colspan="1" %)(% colspan="1" %) 143 143 ((( 144 - Labels265 +Parents 145 145 )))|(% colspan="1" %)(% colspan="1" %) 146 146 ((( 147 - UNDEFINED268 + 148 148 ))) 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 +[[Additional Port Space>>doc:||anchor="addPortSpace"]] 353 +)))|(% colspan="1" %)(% colspan="1" %) 354 +((( 355 +de.cau.cs.kieler.additionalPortSpace 356 +)))|(% colspan="1" %)(% colspan="1" %) 357 +((( 358 +Margins 359 +)))|(% colspan="1" %)(% colspan="1" %) 360 +((( 361 +Nodes 362 +)))|(% colspan="1" %)(% colspan="1" %) 363 +((( 364 +0, 0, 0, 0 365 +))) 366 +|(% colspan="1" %)(% colspan="1" %) 367 +((( 368 +Animate 369 +)))|(% colspan="1" %)(% colspan="1" %) 370 +((( 371 +de.cau.cs.kieler.animate 372 +)))|(% colspan="1" %)(% colspan="1" %) 373 +((( 374 +Boolean 375 +)))|(% colspan="1" %)(% colspan="1" %) 376 +((( 377 +Parents 378 +)))|(% colspan="1" %)(% colspan="1" %) 379 +((( 380 +true 381 +))) 382 +|(% colspan="1" %)(% colspan="1" %) 383 +((( 384 +Animation Time Factor 385 +)))|(% colspan="1" %)(% colspan="1" %) 386 +((( 387 +de.cau.cs.kieler.animTimeFactor 388 +)))|(% colspan="1" %)(% colspan="1" %) 389 +((( 390 +Int 391 +)))|(% colspan="1" %)(% colspan="1" %) 392 +((( 393 +Parents 394 +)))|(% colspan="1" %)(% colspan="1" %) 395 +((( 396 +100 397 +))) 398 +|(% colspan="1" %)(% colspan="1" %) 399 +((( 400 +[[Comment Box>>doc:||anchor="commentBox"]] 401 +)))|(% colspan="1" %)(% colspan="1" %) 402 +((( 403 +de.cau.cs.kieler.commentBox 404 +)))|(% colspan="1" %)(% colspan="1" %) 405 +((( 406 +Boolean 407 +)))|(% colspan="1" %)(% colspan="1" %) 408 +((( 409 +Nodes 410 +)))|(% colspan="1" %)(% colspan="1" %) 411 +((( 412 +false 413 +))) 149 149 |((( 150 -[[ Edge Routing>>doc:||anchor="edgeRouting"]]415 +[[Diagram Type>>doc:||anchor="diagramType"]] 151 151 )))|((( 152 -de.cau.cs.kieler. edgeRouting417 +de.cau.cs.kieler.diagramType 153 153 )))|((( 154 - Enum419 +String 155 155 )))|((( 156 156 Parents 157 157 )))|((( 158 - UNDEFINED423 + 159 159 ))) 425 +|((( 426 +Edge Label Placement 427 +)))|((( 428 +de.cau.cs.kieler.edgeLabelPlacement 429 +)))|((( 430 +Enum 431 +)))|((( 432 +Labels 433 +)))|((( 434 + 435 +))) 160 160 |(% colspan="1" %)(% colspan="1" %) 161 161 ((( 162 162 Edge Type ... ... @@ -173,17 +173,6 @@ 173 173 ((( 174 174 NONE 175 175 ))) 176 -|((( 177 -Expand Nodes 178 -)))|((( 179 -de.cau.cs.kieler.expandNodes 180 -)))|((( 181 -Boolean 182 -)))|((( 183 -Parents 184 -)))|((( 185 -false 186 -))) 187 187 |(% colspan="1" %)(% colspan="1" %) 188 188 ((( 189 189 Font Name ... ... @@ -218,7 +218,7 @@ 218 218 ))) 219 219 |(% colspan="1" %)(% colspan="1" %) 220 220 ((( 221 -Hypernode 486 +[[Hypernode>>doc:||anchor="hypernode"]] 222 222 )))|(% colspan="1" %)(% colspan="1" %) 223 223 ((( 224 224 de.cau.cs.kieler.hypernode ... ... @@ -232,50 +232,53 @@ 232 232 ((( 233 233 false 234 234 ))) 235 -|((( 236 -Interactive 237 -)))|((( 238 -de.cau.cs.kieler.interactive 239 -)))|((( 500 +|(% colspan="1" %)(% colspan="1" %) 501 +((( 502 +Layout Ancestors 503 +)))|(% colspan="1" %)(% colspan="1" %) 504 +((( 505 +de.cau.cs.kieler.layoutAncestors 506 +)))|(% colspan="1" %)(% colspan="1" %) 507 +((( 240 240 Boolean 241 -)))|((( 509 +)))|(% colspan="1" %)(% colspan="1" %) 510 +((( 242 242 Parents 243 -)))|((( 512 +)))|(% colspan="1" %)(% colspan="1" %) 513 +((( 244 244 false 245 245 ))) 246 -|((( 247 -Label Spacing 248 -)))|((( 249 -de.cau.cs.kieler.labelSpacing 250 -)))|((( 251 -Float 252 -)))|((( 253 -Edges 254 -Nodes 255 -)))|((( 256 --1.0 257 -))) 258 -|((( 259 -Layout Hierarchy 260 -)))|((( 261 -de.cau.cs.kieler.layoutHierarchy 262 -)))|((( 263 -Boolean 264 -)))|((( 516 +|(% colspan="1" %)(% colspan="1" %) 517 +((( 518 +Maximal Animation Time 519 +)))|(% colspan="1" %)(% colspan="1" %) 520 +((( 521 +de.cau.cs.kieler.maxAnimTim 522 +)))|(% colspan="1" %)(% colspan="1" %) 523 +((( 524 +Int 525 +)))|(% colspan="1" %)(% colspan="1" %) 526 +((( 265 265 Parents 266 -)))|((( 267 -false 528 +)))|(% colspan="1" %)(% colspan="1" %) 529 +((( 530 +4000 268 268 ))) 269 -|((( 270 -Layout Algorithm 271 -)))|((( 272 -de.cau.cs.kieler.algorithm 273 -)))|((( 274 -String 275 -)))|((( 532 +|(% colspan="1" %)(% colspan="1" %) 533 +((( 534 +Minimal Animation Time 535 +)))|(% colspan="1" %)(% colspan="1" %) 536 +((( 537 +de.cau.cs.kieler.minAnimTim 538 +)))|(% colspan="1" %)(% colspan="1" %) 539 +((( 540 +Int 541 +)))|(% colspan="1" %)(% colspan="1" %) 542 +((( 276 276 Parents 277 -)))|((( 278 - 544 +)))|(% colspan="1" %)(% colspan="1" %) 545 +((( 546 +400 279 279 ))) 280 280 |(% colspan="1" %)(% colspan="1" %) 281 281 ((( ... ... @@ -313,7 +313,7 @@ 313 313 ))) 314 314 |(% colspan="1" %)(% colspan="1" %) 315 315 ((( 316 -No Layout 584 +[[No Layout>>doc:||anchor="noLayout"]] 317 317 )))|(% colspan="1" %)(% colspan="1" %) 318 318 ((( 319 319 de.cau.cs.kieler.noLayout ... ... @@ -329,49 +329,22 @@ 329 329 ))) 330 330 |(% colspan="1" %)(% colspan="1" %) 331 331 ((( 332 - NodeLabel Placement600 +Port Index 333 333 )))|(% colspan="1" %)(% colspan="1" %) 334 334 ((( 335 -de.cau.cs.kieler. nodeLabelPlacement603 +de.cau.cs.kieler.portIndex 336 336 )))|(% colspan="1" %)(% colspan="1" %) 337 337 ((( 338 - EnumSet606 +Int 339 339 )))|(% colspan="1" %)(% colspan="1" %) 340 340 ((( 341 - Nodes609 +Ports 342 342 )))|(% colspan="1" %)(% colspan="1" %) 343 343 ((( 344 344 345 345 ))) 346 -|((( 347 -Port Constraints 348 -)))|((( 349 -de.cau.cs.kieler.portConstraints 350 -)))|((( 351 -Enum 352 -)))|((( 353 -Nodes 354 -)))|((( 355 -UNDEFINED 356 -))) 357 357 |(% colspan="1" %)(% colspan="1" %) 358 358 ((( 359 -Port Label Placement 360 -)))|(% colspan="1" %)(% colspan="1" %) 361 -((( 362 -de.cau.cs.kieler.portLabelPlacement 363 -)))|(% colspan="1" %)(% colspan="1" %) 364 -((( 365 -Enum 366 -)))|(% colspan="1" %)(% colspan="1" %) 367 -((( 368 -Nodes 369 -)))|(% colspan="1" %)(% colspan="1" %) 370 -((( 371 -OUTSIDE 372 -))) 373 -|(% colspan="1" %)(% colspan="1" %) 374 -((( 375 375 [[Port Offset>>doc:||anchor="portOffset"]] 376 376 )))|(% colspan="1" %)(% colspan="1" %) 377 377 ((( ... ... @@ -400,57 +400,16 @@ 400 400 Ports 401 401 )))|(% colspan="1" %)(% colspan="1" %) 402 402 ((( 403 -UNDEFINED 404 -))) 405 -|((( 406 -Position 407 -)))|((( 408 -de.cau.cs.kieler.position 409 -)))|((( 410 -Object 411 -)))|((( 412 -Labels 413 -Nodes 414 -Ports 415 -)))|((( 416 416 417 417 ))) 418 -|((( 419 -Priority 420 -)))|((( 421 -de.cau.cs.kieler.priority 422 -)))|((( 423 -Int 424 -)))|((( 425 -Edges 426 -Nodes 427 -)))|((( 428 - 429 -))) 430 430 |(% colspan="1" %)(% colspan="1" %) 431 431 ((( 432 - Randomization Seed648 +Progress Bar 433 433 )))|(% colspan="1" %)(% colspan="1" %) 434 434 ((( 435 -de.cau.cs.kieler.r andomSeed651 +de.cau.cs.kieler.progressBar 436 436 )))|(% colspan="1" %)(% colspan="1" %) 437 437 ((( 438 -Int 439 -)))|(% colspan="1" %)(% colspan="1" %) 440 -((( 441 -Parents 442 -)))|(% colspan="1" %)(% colspan="1" %) 443 -((( 444 - 445 -))) 446 -|(% colspan="1" %)(% colspan="1" %) 447 -((( 448 -Separate Connected Components 449 -)))|(% colspan="1" %)(% colspan="1" %) 450 -((( 451 -de.cau.cs.kieler.separateConnComp 452 -)))|(% colspan="1" %)(% colspan="1" %) 453 -((( 454 454 Boolean 455 455 )))|(% colspan="1" %)(% colspan="1" %) 456 456 ((( ... ... @@ -457,69 +457,145 @@ 457 457 Parents 458 458 )))|(% colspan="1" %)(% colspan="1" %) 459 459 ((( 460 - 660 +false 461 461 ))) 462 462 |(% colspan="1" %)(% colspan="1" %) 463 463 ((( 464 -S izeConstraint664 +Scale Factor 465 465 )))|(% colspan="1" %)(% colspan="1" %) 466 466 ((( 467 -de.cau.cs.kieler.s izeConstraint667 +de.cau.cs.kieler.scaleFactor 468 468 )))|(% colspan="1" %)(% colspan="1" %) 469 469 ((( 470 - EnumSet670 +Float 471 471 )))|(% colspan="1" %)(% colspan="1" %) 472 472 ((( 473 473 Nodes 474 474 )))|(% colspan="1" %)(% colspan="1" %) 475 475 ((( 476 - 676 +1.0 477 477 ))) 478 478 |(% colspan="1" %)(% colspan="1" %) 479 479 ((( 480 - Size Options680 +Thickness 481 481 )))|(% colspan="1" %)(% colspan="1" %) 482 482 ((( 483 -de.cau.cs.kieler. sizeOptions683 +de.cau.cs.kieler.thickness 484 484 )))|(% colspan="1" %)(% colspan="1" %) 485 485 ((( 486 - EnumSet686 +Float 487 487 )))|(% colspan="1" %)(% colspan="1" %) 488 488 ((( 489 - Nodes689 +Edges 490 490 )))|(% colspan="1" %)(% colspan="1" %) 491 491 ((( 492 - DEFAULT_MINIMUM_SIZE692 +1.0 493 493 ))) 494 494 |(% colspan="1" %)(% colspan="1" %) 495 495 ((( 496 - Spacing696 +Zoom to Fit 497 497 )))|(% colspan="1" %)(% colspan="1" %) 498 498 ((( 499 -de.cau.cs.kieler. spacing699 +de.cau.cs.kieler.zoomToFit 500 500 )))|(% colspan="1" %)(% colspan="1" %) 501 501 ((( 502 - Float702 +Boolean 503 503 )))|(% colspan="1" %)(% colspan="1" %) 504 504 ((( 505 505 Parents 506 506 )))|(% colspan="1" %)(% colspan="1" %) 507 507 ((( 508 - -1.0708 +false 509 509 ))) 510 510 511 -= The MostImportantOptions =711 +=== Layout Output Properties === 512 512 513 - **TODO:**Write abitofdocumentationaboutthemostimportantlayout optionsand howtouse them,possiblywith asimpleexample orsomething.713 +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 514 514 715 +|=((( 716 +Property 717 +)))|=((( 718 +ID 719 +)))|=((( 720 +Type 721 +)))|=((( 722 +Applies to 723 +))) 724 +|((( 725 +[[Edge Routing>>doc:||anchor="edgeRouting"]] 726 +)))|((( 727 +de.cau.cs.kieler.edgeRouting 728 +)))|((( 729 +Enum 730 +)))|((( 731 +Edges 732 +))) 733 +|((( 734 +Junction Points 735 +)))|((( 736 +de.cau.cs.kieler.junctionPoints 737 +)))|((( 738 +Object 739 +)))|((( 740 +Edges 741 +))) 742 + 743 + 744 + 515 515 = Detailed Documentation = 516 516 517 517 This section explains every layout option in more detail. 518 518 519 -== EdgeRouting==749 +== The Most Important Options == 520 520 751 +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. 521 521 753 +=== Layout Algorithm === 522 522 755 +{{id name="layoutAlgorithm"/}} 756 + 757 +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. 758 + 759 +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. 760 + 761 +[[image:attach:layout_algorithm.png]] 762 + 763 +==== Available Algorithms and Libraries ==== 764 + 765 +* **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. 766 +* **Randomizer** - Distributes the nodes randomly; not very useful, but it can show how important a good layout is for understanding a graph. 767 +* ((( 768 +**Box Layout** - Ignores edges, places all nodes in rows. Can be used to layout collections of unconnected boxes, such as Statechart regions. 769 +))) 770 +* **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. 771 +* **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. 772 +* **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. 773 + 774 +==== Predefined Layout Types ==== 775 + 776 +* **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. 777 +* **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. 778 +* **Force** - Layout algorithms that follow physical analogies by simulating a system of attractive and repulsive forces. 779 +* **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. 780 +* **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. 781 + 782 +=== Diagram Type === 783 + 784 +{{id name="diagramType"/}} 785 + 786 +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. 787 + 788 +The following diagram types are predefined: 789 + 790 +* **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. 791 +* **State Machine** - All kinds of state machines, automata, and activity diagrams. Examples: [[doc:SCCharts SyncCharts]], UML Activity diagrams. 792 +* **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)]]. 793 +* **Class Diagram** - Class diagrams such as Ecore diagrams for the [[EMF>>url:http://www.eclipse.org/modeling/emf/||shape="rect"]] or UML Class diagrams. 794 +* **Use Case Diagram** - Use case diagrams as defined by the UML. 795 +* **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]]. 796 + 797 +=== Edge Routing === 798 + 523 523 {{id name="edgeRouting"/}} 524 524 525 525 This option influences the way in which edges are routed between the nodes they connect. The following settings are available: ... ... @@ -527,18 +527,76 @@ 527 527 * POLYLINE 528 528 Edges consist of one or more segments defined by a list of bend points. 529 529 * ORTHOGONAL 530 -Edges are routed orthogonally, meaning that each segment of an edge runs either horizontally or vertically , but never at an angle.531 -* SPLINE 532 -Edges are routed as splines (smooth curves). (% style="color: rgb(153,51,0);" %)**TODO:** Add more documentation on how the returned bend points are to be interpreted.806 +Edges are routed orthogonally, meaning that each segment of an edge runs either horizontally or vertically. 807 +* SPLINES 808 +Edges are routed as splines (smooth curves). 533 533 * UNDEFINED 534 -No particular edge routing style is selected. The result producedbythe layout algorithmmay be undefined.810 +No particular edge routing style is selected. Usually this value points to the default setting of the selected layout algorithm. 535 535 536 - (% style="color: rgb(153,51,0);" %)**TODO:** Add animageillustratingthedifferent routingstyles.812 +[[image:attach:edge_routing.png]] 537 537 538 - ==PortOffset==814 +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: 539 539 816 +1. Start at the source point of the edge. 817 +1. As long as there are at least three bend points left: 818 +11. Draw a cubic spline segment to the third bend point with the other two bend points as control points. 819 +11. Use the third bend point as start point for the next segment. 820 +11. Consume the three bend points and proceed to the next segment. 821 +1. Check the number of remaining bend points: 822 +11. Two bend points – draw a cubic spline segment to the target point of the edge. 823 +11. One bend point – draw a quadratic spline segment to the target point of the edge. 824 +11. No bend point – draw a straight line to the target point of the edge. 540 540 826 +== Other Options == 541 541 828 +=== Additional Port Space === 829 + 830 +{{id name="addPortSpace"/}} 831 + 832 +This option controls additional port space left around the set of ports on each side: 833 + 834 + 835 + 836 +=== Alignment === 837 + 838 +{{id name="alignment"/}} 839 + 840 +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. 841 + 842 +=== Aspect Ratio === 843 + 844 +{{id name="aspectRatio"/}} 845 + 846 +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. 847 + 848 +=== Comment Box === 849 + 850 +{{id name="commentBox"/}} 851 + 852 +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. 853 + 854 +[[image:attach:comment_box.png]] 855 + 856 +=== (% style="line-height: 1.5625;" %)Hypernode(%%) === 857 + 858 +{{id name="hypernode"/}} 859 + 860 +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. 861 + 862 +=== Layout Hierarchy === 863 + 864 +{{id name="layoutHierarchy"/}} 865 + 866 +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. 867 + 868 +=== No Layout === 869 + 870 +{{id name="noLayout"/}} 871 + 872 +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. 873 + 874 +=== Port Offset === 875 + 542 542 {{id name="portOffset"/}} 543 543 544 544 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. ... ... @@ -547,3 +547,9 @@ 547 547 548 548 * The port constraints on a node are set to FREE, FIXED_SIDES or FIXED_ORDER. 549 549 * The port constraints on a node are set to FIXED_RATIO or FIXED_POS, and the size of the node is not fixed. (Note that this is especially true for ports of compound nodes.) 884 + 885 +=== Port Spacing === 886 + 887 +{{id name="portSpacing"/}} 888 + 889 +The port spacing determines how much space KLay Layered should leave between the ports of each side. This option is only relevant if the node size depends on the ports, that is, if the size constraints include {{code language="none"}}SizeConstraint.PORTS{{/code}}.
- Confluence.Code.ConfluencePageClass[0]
-
- Id
-
... ... @@ -1,1 +1,1 @@ 1 -94 699641 +9470237 - URL
-
... ... @@ -1,1 +1,1 @@ 1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/94 69964/KIML Layout Options1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/9470237/KIML Layout Options