Changes for page KIML Layout Options
Last modified by Alexander Schulz-Rosengarten on 2023/09/11 16:17
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 )))|=((( ... ... @@ -74,29 +74,46 @@ 74 74 )))|((( 75 75 Parents 76 76 )))|((( 77 - -1.079 + 78 78 ))) 79 -|(% colspan="1" %)(% colspan="1" %) 80 -((( 81 -Comment Box 82 -)))|(% colspan="1" %)(% colspan="1" %) 83 -((( 84 -de.cau.cs.kieler.commentBox 85 -)))|(% colspan="1" %)(% colspan="1" %) 86 -((( 81 +|((( 82 +Debug Mode 83 +)))|((( 84 +de.cau.cs.kieler.debugMode 85 +)))|((( 87 87 Boolean 88 -)))|(% colspan="1" %)(% colspan="1" %) 89 -((( 90 -Nodes 91 -)))|(% colspan="1" %)(% colspan="1" %) 92 -((( 87 +)))|((( 88 +Parents 89 +)))|((( 93 93 false 94 94 ))) 95 95 |((( 96 -De bug Mode93 +Direction 97 97 )))|((( 98 -de.cau.cs.kieler.de bugMode95 +de.cau.cs.kieler.direction 99 99 )))|((( 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 +)))|((( 100 100 Boolean 101 101 )))|((( 102 102 Parents ... ... @@ -103,99 +103,179 @@ 103 103 )))|((( 104 104 false 105 105 ))) 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 +))) 106 106 |(% colspan="1" %)(% colspan="1" %) 107 107 ((( 108 - [[Diagram Type>>doc:||anchor="diagramType"]]172 +Node Label Placement 109 109 )))|(% colspan="1" %)(% colspan="1" %) 110 110 ((( 111 -de.cau.cs.kieler.d iagramType175 +de.cau.cs.kieler.nodeLabelPlacement 112 112 )))|(% colspan="1" %)(% colspan="1" %) 113 113 ((( 114 -St ring178 +EnumSet 115 115 )))|(% colspan="1" %)(% colspan="1" %) 116 116 ((( 117 - 181 +Nodes 118 118 )))|(% colspan="1" %)(% colspan="1" %) 119 119 ((( 120 120 121 121 ))) 122 122 |((( 123 - Direction187 +Port Constraints 124 124 )))|((( 125 -de.cau.cs.kieler. direction189 +de.cau.cs.kieler.portConstraints 126 126 )))|((( 127 127 Enum 128 128 )))|((( 129 - Parents193 +Nodes 130 130 )))|((( 131 - UNDEFINED195 + 132 132 ))) 133 133 |(% colspan="1" %)(% colspan="1" %) 134 134 ((( 135 - EdgeLabel Placement199 +Port Label Placement 136 136 )))|(% colspan="1" %)(% colspan="1" %) 137 137 ((( 138 -de.cau.cs.kieler. edgeLabelPlacement202 +de.cau.cs.kieler.portLabelPlacement 139 139 )))|(% colspan="1" %)(% colspan="1" %) 140 140 ((( 141 141 Enum 142 142 )))|(% colspan="1" %)(% colspan="1" %) 143 143 ((( 144 - Labels208 +Nodes 145 145 )))|(% colspan="1" %)(% colspan="1" %) 146 146 ((( 147 -U NDEFINED211 +OUTSIDE 148 148 ))) 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 +((( 227 + 228 +))) 149 149 |((( 150 - [[Edge Routing>>doc:||anchor="edgeRouting"]]230 +Position 151 151 )))|((( 152 -de.cau.cs.kieler. edgeRouting232 +de.cau.cs.kieler.position 153 153 )))|((( 154 - Enum234 +Object 155 155 )))|((( 156 -Parents 236 +Labels 237 +Nodes 238 +Ports 157 157 )))|((( 158 - UNDEFINED240 + 159 159 ))) 242 +|((( 243 +Priority 244 +)))|((( 245 +de.cau.cs.kieler.priority 246 +)))|((( 247 +Int 248 +)))|((( 249 +Edges 250 +Nodes 251 +)))|((( 252 + 253 +))) 160 160 |(% colspan="1" %)(% colspan="1" %) 161 161 ((( 162 - EdgeType256 +Randomization Seed 163 163 )))|(% colspan="1" %)(% colspan="1" %) 164 164 ((( 165 -de.cau.cs.kieler. edgeType259 +de.cau.cs.kieler.randomSeed 166 166 )))|(% colspan="1" %)(% colspan="1" %) 167 167 ((( 168 - Enum262 +Int 169 169 )))|(% colspan="1" %)(% colspan="1" %) 170 170 ((( 171 - Edges265 +Parents 172 172 )))|(% colspan="1" %)(% colspan="1" %) 173 173 ((( 174 - NONE268 + 175 175 ))) 176 -|((( 177 -Expand Nodes 178 -)))|((( 179 -de.cau.cs.kieler.expandNodes 180 -)))|((( 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 +((( 181 181 Boolean 182 -)))|((( 279 +)))|(% colspan="1" %)(% colspan="1" %) 280 +((( 183 183 Parents 184 -)))|((( 185 -false 282 +)))|(% colspan="1" %)(% colspan="1" %) 283 +((( 284 + 186 186 ))) 187 187 |(% colspan="1" %)(% colspan="1" %) 188 188 ((( 189 - FontName288 +Size Constraint 190 190 )))|(% colspan="1" %)(% colspan="1" %) 191 191 ((( 192 -de.cau.cs.kieler. fontName291 +de.cau.cs.kieler.sizeConstraint 193 193 )))|(% colspan="1" %)(% colspan="1" %) 194 194 ((( 195 -St ring294 +EnumSet 196 196 )))|(% colspan="1" %)(% colspan="1" %) 197 197 ((( 198 - Labels297 +Nodes 199 199 )))|(% colspan="1" %)(% colspan="1" %) 200 200 ((( 201 201 ... ... @@ -202,31 +202,95 @@ 202 202 ))) 203 203 |(% colspan="1" %)(% colspan="1" %) 204 204 ((( 205 - FontSize304 +Size Options 206 206 )))|(% colspan="1" %)(% colspan="1" %) 207 207 ((( 208 -de.cau.cs.kieler. fontSize307 +de.cau.cs.kieler.sizeOptions 209 209 )))|(% colspan="1" %)(% colspan="1" %) 210 210 ((( 211 - Int310 +EnumSet 212 212 )))|(% colspan="1" %)(% colspan="1" %) 213 213 ((( 214 - Labels313 +Nodes 215 215 )))|(% colspan="1" %)(% colspan="1" %) 216 216 ((( 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 +((( 217 217 218 218 ))) 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 +))) 219 219 |(% colspan="1" %)(% colspan="1" %) 220 220 ((( 221 - Hypernode352 +Animate 222 222 )))|(% colspan="1" %)(% colspan="1" %) 223 223 ((( 224 -de.cau.cs.kieler. hypernode355 +de.cau.cs.kieler.animate 225 225 )))|(% colspan="1" %)(% colspan="1" %) 226 226 ((( 227 227 Boolean 228 228 )))|(% colspan="1" %)(% colspan="1" %) 229 229 ((( 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 +((( 230 230 Nodes 231 231 )))|(% colspan="1" %)(% colspan="1" %) 232 232 ((( ... ... @@ -233,96 +233,103 @@ 233 233 false 234 234 ))) 235 235 |((( 236 - Interactive399 +[[Diagram Type>>doc:||anchor="diagramType"]] 237 237 )))|((( 238 -de.cau.cs.kieler.i nteractive401 +de.cau.cs.kieler.diagramType 239 239 )))|((( 240 - Boolean403 +String 241 241 )))|((( 242 242 Parents 243 243 )))|((( 244 - false407 + 245 245 ))) 246 246 |((( 247 -Label Spacing410 +Edge Label Placement 248 248 )))|((( 249 -de.cau.cs.kieler. labelSpacing412 +de.cau.cs.kieler.edgeLabelPlacement 250 250 )))|((( 251 - Float414 +Enum 252 252 )))|((( 253 -Edges 254 -Nodes 416 +Labels 255 255 )))|((( 256 - -1.0418 + 257 257 ))) 258 -|((( 259 -Layout Hierarchy 260 -)))|((( 261 -de.cau.cs.kieler.layoutHierarchy 262 -)))|((( 263 -Boolean 264 -)))|((( 265 -Parents 266 -)))|((( 267 -false 420 +|(% colspan="1" %)(% colspan="1" %) 421 +((( 422 +Edge Type 423 +)))|(% colspan="1" %)(% colspan="1" %) 424 +((( 425 +de.cau.cs.kieler.edgeType 426 +)))|(% colspan="1" %)(% colspan="1" %) 427 +((( 428 +Enum 429 +)))|(% colspan="1" %)(% colspan="1" %) 430 +((( 431 +Edges 432 +)))|(% colspan="1" %)(% colspan="1" %) 433 +((( 434 +NONE 268 268 ))) 269 -|((( 270 -[[Layout Algorithm>>doc:||anchor="layoutAlgorithm"]] 271 -)))|((( 272 -de.cau.cs.kieler.algorithm 273 -)))|((( 436 +|(% colspan="1" %)(% colspan="1" %) 437 +((( 438 +Font Name 439 +)))|(% colspan="1" %)(% colspan="1" %) 440 +((( 441 +de.cau.cs.kieler.fontName 442 +)))|(% colspan="1" %)(% colspan="1" %) 443 +((( 274 274 String 275 -)))|((( 276 -Parents 277 -)))|((( 445 +)))|(% colspan="1" %)(% colspan="1" %) 446 +((( 447 +Labels 448 +)))|(% colspan="1" %)(% colspan="1" %) 449 +((( 278 278 279 279 ))) 280 280 |(% colspan="1" %)(% colspan="1" %) 281 281 ((( 282 - MinimalHeight454 +Font Size 283 283 )))|(% colspan="1" %)(% colspan="1" %) 284 284 ((( 285 -de.cau.cs.kieler. minHeight457 +de.cau.cs.kieler.fontSize 286 286 )))|(% colspan="1" %)(% colspan="1" %) 287 287 ((( 288 - Float460 +Int 289 289 )))|(% colspan="1" %)(% colspan="1" %) 290 290 ((( 291 -Nodes 292 -Parents 463 +Labels 293 293 )))|(% colspan="1" %)(% colspan="1" %) 294 294 ((( 295 - 0.0466 + 296 296 ))) 297 297 |(% colspan="1" %)(% colspan="1" %) 298 298 ((( 299 - Minimal Width470 +[[Hypernode>>doc:||anchor="hypernode"]] 300 300 )))|(% colspan="1" %)(% colspan="1" %) 301 301 ((( 302 -de.cau.cs.kieler. minWidth473 +de.cau.cs.kieler.hypernode 303 303 )))|(% colspan="1" %)(% colspan="1" %) 304 304 ((( 305 - Float476 +Boolean 306 306 )))|(% colspan="1" %)(% colspan="1" %) 307 307 ((( 308 308 Nodes 309 -Parents 310 310 )))|(% colspan="1" %)(% colspan="1" %) 311 311 ((( 312 - 0.0482 +false 313 313 ))) 314 314 |(% colspan="1" %)(% colspan="1" %) 315 315 ((( 316 - NoLayout486 +Layout Ancestors 317 317 )))|(% colspan="1" %)(% colspan="1" %) 318 318 ((( 319 -de.cau.cs.kieler. noLayout489 +de.cau.cs.kieler.layoutAncestors 320 320 )))|(% colspan="1" %)(% colspan="1" %) 321 321 ((( 322 322 Boolean 323 323 )))|(% colspan="1" %)(% colspan="1" %) 324 324 ((( 325 - 495 +Parents 326 326 )))|(% colspan="1" %)(% colspan="1" %) 327 327 ((( 328 328 false ... ... @@ -329,116 +329,114 @@ 329 329 ))) 330 330 |(% colspan="1" %)(% colspan="1" %) 331 331 ((( 332 - Node LabelPlacement502 +Maximal Animation Time 333 333 )))|(% colspan="1" %)(% colspan="1" %) 334 334 ((( 335 -de.cau.cs.kieler. nodeLabelPlacement505 +de.cau.cs.kieler.maxAnimTim 336 336 )))|(% colspan="1" %)(% colspan="1" %) 337 337 ((( 338 - EnumSet508 +Int 339 339 )))|(% colspan="1" %)(% colspan="1" %) 340 340 ((( 341 - Nodes511 +Parents 342 342 )))|(% colspan="1" %)(% colspan="1" %) 343 343 ((( 344 - 514 +4000 345 345 ))) 346 -|((( 347 -Port Constraints 348 -)))|((( 349 -de.cau.cs.kieler.portConstraints 350 -)))|((( 351 -Enum 352 -)))|((( 353 -Nodes 354 -)))|((( 355 -UNDEFINED 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 +((( 527 +Parents 528 +)))|(% colspan="1" %)(% colspan="1" %) 529 +((( 530 +400 356 356 ))) 357 357 |(% colspan="1" %)(% colspan="1" %) 358 358 ((( 359 - Port LabelPlacement534 +Minimal Height 360 360 )))|(% colspan="1" %)(% colspan="1" %) 361 361 ((( 362 -de.cau.cs.kieler. portLabelPlacement537 +de.cau.cs.kieler.minHeight 363 363 )))|(% colspan="1" %)(% colspan="1" %) 364 364 ((( 365 - Enum540 +Float 366 366 )))|(% colspan="1" %)(% colspan="1" %) 367 367 ((( 368 368 Nodes 544 +Parents 369 369 )))|(% colspan="1" %)(% colspan="1" %) 370 370 ((( 371 - OUTSIDE547 +0.0 372 372 ))) 373 373 |(% colspan="1" %)(% colspan="1" %) 374 374 ((( 375 - [[PortOffset>>doc:||anchor="portOffset"]]551 +Minimal Width 376 376 )))|(% colspan="1" %)(% colspan="1" %) 377 377 ((( 378 -de.cau.cs.kieler. offset554 +de.cau.cs.kieler.minWidth 379 379 )))|(% colspan="1" %)(% colspan="1" %) 380 380 ((( 381 381 Float 382 382 )))|(% colspan="1" %)(% colspan="1" %) 383 383 ((( 384 -Ports 560 +Nodes 561 +Parents 385 385 )))|(% colspan="1" %)(% colspan="1" %) 386 386 ((( 387 - 564 +0.0 388 388 ))) 389 389 |(% colspan="1" %)(% colspan="1" %) 390 390 ((( 391 - PortSide568 +[[No Layout>>doc:||anchor="noLayout"]] 392 392 )))|(% colspan="1" %)(% colspan="1" %) 393 393 ((( 394 -de.cau.cs.kieler. portSide571 +de.cau.cs.kieler.noLayout 395 395 )))|(% colspan="1" %)(% colspan="1" %) 396 396 ((( 397 - Enum574 +Boolean 398 398 )))|(% colspan="1" %)(% colspan="1" %) 399 399 ((( 400 - Ports577 + 401 401 )))|(% colspan="1" %)(% colspan="1" %) 402 402 ((( 403 - UNDEFINED580 +false 404 404 ))) 405 -|((( 406 -Position 407 -)))|((( 408 -de.cau.cs.kieler.position 409 -)))|((( 410 -Object 411 -)))|((( 412 -Labels 413 -Nodes 582 +|(% colspan="1" %)(% colspan="1" %) 583 +((( 584 +Port Index 585 +)))|(% colspan="1" %)(% colspan="1" %) 586 +((( 587 +de.cau.cs.kieler.portIndex 588 +)))|(% colspan="1" %)(% colspan="1" %) 589 +((( 590 +Int 591 +)))|(% colspan="1" %)(% colspan="1" %) 592 +((( 414 414 Ports 415 -)))|((( 594 +)))|(% colspan="1" %)(% colspan="1" %) 595 +((( 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 - RandomizationSeed600 +[[Port Offset>>doc:||anchor="portOffset"]] 433 433 )))|(% colspan="1" %)(% colspan="1" %) 434 434 ((( 435 -de.cau.cs.kieler. randomSeed603 +de.cau.cs.kieler.offset 436 436 )))|(% colspan="1" %)(% colspan="1" %) 437 437 ((( 438 - Int606 +Float 439 439 )))|(% colspan="1" %)(% colspan="1" %) 440 440 ((( 441 -P arents609 +Ports 442 442 )))|(% colspan="1" %)(% colspan="1" %) 443 443 ((( 444 444 ... ... @@ -445,16 +445,16 @@ 445 445 ))) 446 446 |(% colspan="1" %)(% colspan="1" %) 447 447 ((( 448 - SeparateConnectedComponents616 +Port Side 449 449 )))|(% colspan="1" %)(% colspan="1" %) 450 450 ((( 451 -de.cau.cs.kieler. separateConnComp619 +de.cau.cs.kieler.portSide 452 452 )))|(% colspan="1" %)(% colspan="1" %) 453 453 ((( 454 - Boolean622 +Enum 455 455 )))|(% colspan="1" %)(% colspan="1" %) 456 456 ((( 457 -P arents625 +Ports 458 458 )))|(% colspan="1" %)(% colspan="1" %) 459 459 ((( 460 460 ... ... @@ -461,76 +461,108 @@ 461 461 ))) 462 462 |(% colspan="1" %)(% colspan="1" %) 463 463 ((( 464 - Size Constraint632 +Progress Bar 465 465 )))|(% colspan="1" %)(% colspan="1" %) 466 466 ((( 467 -de.cau.cs.kieler. sizeConstraint635 +de.cau.cs.kieler.progressBar 468 468 )))|(% colspan="1" %)(% colspan="1" %) 469 469 ((( 470 - EnumSet638 +Boolean 471 471 )))|(% colspan="1" %)(% colspan="1" %) 472 472 ((( 473 - Nodes641 +Parents 474 474 )))|(% colspan="1" %)(% colspan="1" %) 475 475 ((( 476 - 644 +false 477 477 ))) 478 478 |(% colspan="1" %)(% colspan="1" %) 479 479 ((( 480 -S izeOptions648 +Scale Factor 481 481 )))|(% colspan="1" %)(% colspan="1" %) 482 482 ((( 483 -de.cau.cs.kieler.s izeOptions651 +de.cau.cs.kieler.scaleFactor 484 484 )))|(% colspan="1" %)(% colspan="1" %) 485 485 ((( 486 - EnumSet654 +Float 487 487 )))|(% colspan="1" %)(% colspan="1" %) 488 488 ((( 489 489 Nodes 490 490 )))|(% colspan="1" %)(% colspan="1" %) 491 491 ((( 492 - DEFAULT_MINIMUM_SIZE660 +1.0 493 493 ))) 494 494 |(% colspan="1" %)(% colspan="1" %) 495 495 ((( 496 - Spacing664 +Zoom to Fit 497 497 )))|(% colspan="1" %)(% colspan="1" %) 498 498 ((( 499 -de.cau.cs.kieler. spacing667 +de.cau.cs.kieler.zoomToFit 500 500 )))|(% colspan="1" %)(% colspan="1" %) 501 501 ((( 502 - Float670 +Boolean 503 503 )))|(% colspan="1" %)(% colspan="1" %) 504 504 ((( 505 505 Parents 506 506 )))|(% colspan="1" %)(% colspan="1" %) 507 507 ((( 508 - -1.0676 +false 509 509 ))) 510 510 511 -= The MostImportantOptions =679 +=== Layout Output Properties === 512 512 513 - Whilemost layout options are used toaffecthowtheactivelayout algorithmcomputesconcretecoordinatesforthegraphelements,thereare somelayoutoptionsthat havea specialrolein KIML.681 +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 515 -== Layout Algorithm == 683 +|=((( 684 +Property 685 +)))|=((( 686 +ID 687 +)))|=((( 688 +Type 689 +)))|=((( 690 +Applies to 691 +))) 692 +|((( 693 +[[Edge Routing>>doc:||anchor="edgeRouting"]] 694 +)))|((( 695 +de.cau.cs.kieler.edgeRouting 696 +)))|((( 697 +Enum 698 +)))|((( 699 +Edges 700 +))) 701 +|((( 702 +Junction Points 703 +)))|((( 704 +de.cau.cs.kieler.junctionPoints 705 +)))|((( 706 +Object 707 +)))|((( 708 +Edges 709 +))) 516 516 711 + 517 517 713 += Detailed Documentation = 518 518 715 +This section explains every layout option in more detail. 716 + 717 +== The Most Important Options == 718 + 719 +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. 720 + 721 +=== Layout Algorithm === 722 + 519 519 {{id name="layoutAlgorithm"/}} 520 520 521 -The option with identifier {{code language="none"}}de.cau.cs.kieler.algorithm{{/code}} specifies which layout algorithm to use for thecontentofacomposite node. 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.725 +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. 522 522 523 -The following layout ty pes arepredefined:727 +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. 524 524 525 -* **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. 526 -* **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. 527 -* **Force** - Layout algorithms that follow physical analogies by simulating a system of attractive and repulsive forces. 528 -* **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. 529 -* **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. 729 +[[image:attach:layout_algorithm.png]] 530 530 531 -=== Available Algorithms and Libraries === 731 +==== Available Algorithms and Libraries ==== 532 532 533 -* **The [[KLay Project>>doc:Layout Algorithms (KLay)]]** - Java implementations of standard layout approaches, augmented with special processing of graph features such as ports and edgelabels.733 +* **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. 534 534 * **Randomizer** - Distributes the nodes randomly; not very useful, but it can show how important a good layout is for understanding a graph. 535 535 * ((( 536 536 **Box Layout** - Ignores edges, places all nodes in rows. Can be used to layout collections of unconnected boxes, such as Statechart regions. ... ... @@ -539,9 +539,15 @@ 539 539 * **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. 540 540 * **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. 541 541 542 -== DiagramType ==742 +==== Predefined Layout Types ==== 543 543 744 +* **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. 745 +* **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. 746 +* **Force** - Layout algorithms that follow physical analogies by simulating a system of attractive and repulsive forces. 747 +* **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. 748 +* **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. 544 544 750 +=== Diagram Type === 545 545 546 546 {{id name="diagramType"/}} 547 547 ... ... @@ -556,40 +556,65 @@ 556 556 * **Use Case Diagram** - Use case diagrams as defined by the UML. 557 557 * **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]]. 558 558 765 +=== Edge Routing === 766 + 767 +{{id name="edgeRouting"/}} 768 + 769 +This option influences the way in which edges are routed between the nodes they connect. The following settings are available: 770 + 771 +* POLYLINE 772 +Edges consist of one or more segments defined by a list of bend points. 773 +* ORTHOGONAL 774 +Edges are routed orthogonally, meaning that each segment of an edge runs either horizontally or vertically. 775 +* SPLINES 776 +Edges are routed as splines (smooth curves). 777 +* UNDEFINED 778 +No particular edge routing style is selected. Usually this value points to the default setting of the selected layout algorithm. 779 + 780 +[[image:attach:edge_routing.png]] 781 + 782 +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: 783 + 784 +1. Start at the source point of the edge. 785 +1. As long as there are at least three bend points left: 786 +11. Draw a cubic spline segment to the third bend point with the other two bend points as control points. 787 +11. Use the third bend point as start point for the next segment. 788 +11. Consume the three bend points and proceed to the next segment. 789 +1. Check the number of remaining bend points: 790 +11. Two bend points – draw a cubic spline segment to the target point of the edge. 791 +11. One bend point – draw a quadratic spline segment to the target point of the edge. 792 +11. No bend point – draw a straight line to the target point of the edge. 793 + 559 559 == Other Options == 560 560 561 -* **Layout Hierarchy** ({{code language="none"}}de.cau.cs.kieler.layoutHierarchy{{/code}}) - 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. 562 -* **Hypernode** ({{code language="none"}}de.cau.cs.kieler.hypernode{{/code}}) - 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. 563 -* **Comment Box** ({{code language="none"}}de.cau.cs.kieler.commentBox{{/code}}) - A node that is marked as comment box is treated as a label that needs to be placed somewhere. This is different to normal node labels, which are usually regarded as fixed. 564 -* **No Layout** ({{code language="none"}}de.cau.cs.kieler.noLayout{{/code}}) - 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. 796 +=== Comment Box === 565 565 566 - = DetailedDocumentation =798 +{{id name="commentBox"/}} 567 567 568 - Thissection explains everylayout optioninmore detail.800 +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. 569 569 570 - == EdgeRouting==802 +[[image:attach:comment_box.png]] 571 571 804 +=== (% style="line-height: 1.5625;" %)Hypernode(%%) === 572 572 806 +{{id name="hypernode"/}} 573 573 574 - {{id name="edgeRouting"/}}808 +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. 575 575 576 - Thisoption influencesthewayin whichedgesare routed between the nodes theyconnect. The following settings are available:810 +=== Layout Hierarchy === 577 577 578 -* POLYLINE 579 -Edges consist of one or more segments defined by a list of bend points. 580 -* ORTHOGONAL 581 -Edges are routed orthogonally, meaning that each segment of an edge runs either horizontally or vertically, but never at an angle. 582 -* SPLINE 583 -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. 584 -* UNDEFINED 585 -No particular edge routing style is selected. The result produced by the layout algorithm may be undefined. 812 +{{id name="layoutHierarchy"/}} 586 586 587 - (%style="color:rgb(153,51,0);"%)**TODO:** Addanimageillustratingthe differentroutingstyles.814 +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. 588 588 589 -== PortOffset ==816 +=== No Layout === 590 590 818 +{{id name="noLayout"/}} 591 591 820 +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. 592 592 822 +=== Port Offset === 823 + 593 593 {{id name="portOffset"/}} 594 594 595 595 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 -94700 041 +9470016 - URL
-
... ... @@ -1,1 +1,1 @@ 1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/94700 04/KIML Layout Options1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/9470016/KIML Layout Options