Changes for page KIML Layout Options
on 2013/06/03 10:42
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,5 +1,5 @@ 1 1 {{warning}} 2 -This is preliminary documentation. You've been warned. 2 +This is preliminary and incomplete documentation. You've been warned. 3 3 {{/warning}} 4 4 5 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. ... ... @@ -6,8 +6,10 @@ 6 6 7 7 **Contents** 8 8 9 - 10 10 10 + 11 +{{toc/}} 12 + 11 11 = Overview = 12 12 13 13 Beside a human-readable name, layout options are defined by the following properties: ... ... @@ -145,7 +145,7 @@ 145 145 UNDEFINED 146 146 ))) 147 147 |((( 148 -Edge Routing 150 +[[Edge Routing>>doc:||anchor="edgeRouting"]] 149 149 )))|((( 150 150 de.cau.cs.kieler.edgeRouting 151 151 )))|((( ... ... @@ -514,8 +514,29 @@ 514 514 515 515 This section explains every layout option in more detail. 516 516 517 -== PortOffset==519 +== Edge Routing == 518 518 521 + 522 + 523 +{{id name="edgeRouting"/}} 524 + 525 +This option influences the way in which edges are routed between the nodes they connect. The following settings are available: 526 + 527 +* POLYLINE 528 +Edges consist of one or more segments defined by a list of bend points. 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. 533 +* UNDEFINED 534 +No particular edge routing style is selected. The result produced by the layout algorithm may be undefined. 535 + 536 +(% style="color: rgb(153,51,0);" %)**TODO:** Add an image illustrating the different routing styles. 537 + 538 +== Port Offset == 539 + 540 + 541 + 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 - 71111101 +9469964 - URL
-
... ... @@ -1,1 +1,1 @@ 1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/ 7111110/KIML Layout Options1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/9469964/KIML Layout Options