Changes for page KIML

Last modified by Richard Kreissig on 2025/01/30 12:04
<
From version < 3.1 >
edited by msp
on 2013/03/27 16:38
To version < 5.1 >
edited by msp
on 2013/03/27 16:50
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -15,7 +15,7 @@
15 15  11. The checkboxes in the //Options// group can be deactivated -> //Finish//
16 16  1. Commit the new plugin project ((% style="color: rgb(255,0,0);" %)TODO: describe steps to commit plugin projects(%%))
17 17  1. (% style="font-size: 10.0pt;line-height: 13.0pt;" %)Open the file META-INF/MANIFEST.MF //→// //Dependencies// tab(%%)\\
18 -1*. Add the plugins de.cau.cs.kieler.core and de.cau.cs.kieler.kiml to the list of dependencies, then save the file
18 +1*. Add the plugins de.cau.cs.kieler.core and de.cau.cs.kieler.kiml to the list of dependencies, then save the file.
19 19  1. Create a //layout provider// class with the //New →// Class wizard\\
20 20  1*. Package: de.cau.cs.rtprak.<login>.tutorial2
21 21  1*. Name: <Login>LayoutProvider
... ... @@ -75,63 +75,57 @@
75 75   nodeLayouty
76 76  }}}
77 77  )))
78 -* objectSpacing shall be the spacing to be left between each pair of nodes
79 -* borderSpacing shall be the spacing to be left to the borders of the drawing: the first node's coordinates shall be (borderSpacing, borderSpacing)
80 -* At the end of the method, set the width and height of parentLayout so that it is large enough to hold the whole drawing, including borders
81 -* Edges may be ignored for now
78 +* {{code language="none"}}objectSpacing{{/code}} shall be the spacing to be left between each pair of nodes.
79 +* {{code language="none"}}borderSpacing{{/code}} shall be the spacing to be left to the borders of the drawing: the first node's coordinates shall be (borderSpacing, borderSpacing).
80 +* At the end of the method, set the width and height of {{code language="none"}}parentLayout{{/code}} so that it is large enough to hold the whole drawing, including borders.
81 +* Edges may be ignored for now.
82 82  )))
83 83  )))
84 -1. Open the file META-INF/MANIFEST.MF -> //Extensions// tab\\
84 +1. Open the file META-INF/MANIFEST.MF //→// //Extensions// tab\\
85 85  11. Add an extension for de.cau.cs.kieler.kiml.layout.layoutProviders
86 -11. Right-click the extension -> //New// -> //layoutProvider//
87 -11. Set //name// to //<Login> Test Layouter//, //class// to de.cau.cs.rtprak.<login>.exercise1.<Login>LayoutProvider
88 -11. Right-click the new //layoutProvider// -> //New// -> //knownOption//, set //option// to de.cau.cs.kieler.layout.options.minSpacing
89 -11. Add another //knownOption//, set to de.cau.cs.kieler.layout.options.borderSpacing
90 -1. //Run// -> //Run Configurations...// -> right-click //Eclipse Application// -> //New//\\
86 +11. Right-click the extension //→// //New// //→// //layoutProvider//
87 +11. Set //name// to //<Login> Test Layouter//, //class// to de.cau.cs.rtprak.<login>.tutorial2.<Login>LayoutProvider
88 +11. Right-click the new //layoutProvider// //→// //New// //→// //knownOption//, set //option// to de.cau.cs.kieler.spacing
89 +11. Add another //knownOption//, set to de.cau.cs.kieler.borderSpacing
90 +1. //Run// //→// //Run Configurations...// //→// right-click //Eclipse Application// //→// //New//\\
91 91  11. Name: //Layout//
92 -11. For testing the layouter, a new workspace location will be created; you may configure its destination in //Workspace Data// -> //Location//
93 -11. Add the program arguments -debug -consoleLog in the //Arguments// tab
92 +11. For testing the layouter, a new workspace location will be created; you may configure its destination in //Workspace Data// //→// //Location//
93 +11. Add the program arguments {{code language="none"}}-debug -consoleLog{{/code}} in the //Arguments// tab.
94 94  11. Go to //Plug-ins// tab, select //Launch with: plug-ins selected below only//
95 95  11. //Deselect All//, activate //Workspace// checkbox, //Add Required Plug-ins//, //Apply//, //Run//
96 96  1. Test the layouter in the new Eclipse instance:\\
97 -11. //New// -> //Project...// -> //General// -> //Project//, name //test//
98 -11. Right-click test project -> //New// -> //Other...// -> //Graphs Diagram//
99 -11. Create a graph using the palette on the right
100 -11. //Window// -> //Show View// -> //Other...// -> //KIELER// -> //Layout//
101 -11. While the graph diagram is open, set //Layout Provider or Type// in the //Layout// view to //<Login> Test Layouter//
102 -11. Open the additional views //Layout Graph// and //Layout Time//
103 -11. Trigger layout with //KIELER// -> //Layout// or Ctrl+R L (first Ctrl+R, then L) or the button in the toolbar
104 -11. See the direct input and output of your algorithm in the //Layout Graph// view: //Pre-Layout// is the input, //Post-Layout// is the output
105 -11. See the execution time analysis in the //Layout Time// view
97 +11. //New// //→// //Project...// //→// //General// //→// //Project//, name //test//
98 +11. Right-click test project //→// //New// //→// //Other...// //→// //KEG Diagram// ((% style="color: rgb(255,0,0);" %)TODO: if graphs shall be created in another way, describe it here(%%))
99 +11. Create a graph using the palette on the right.
100 +11. //Window// //→// //Show View// //→// //Other...// //→// //KIELER// //→// //Layout//
101 +11. While the graph diagram is open, set //Layout Provider or Type// in the //Layout// view to //<Login> Test Layouter.//
102 +11. Open the additional views //Layout Graph// and //Layout Time.//
103 +11. Trigger layout with the //KIELER Layout// button in the toolbar or Ctrl+R L (first Ctrl+R, then L).
104 +11. See the direct input and output of your algorithm in the //Layout Graph// view.
105 +11. See the execution time analysis in the //Layout Time// view.
106 106  1. (((
107 -Implement another class //EdgeRouter// with superclass de.cau.cs.kieler.core.alg.AbstractAlgorithm
107 +Implement another class //EdgeRouter//.
108 108  1. Add the following method:(% class="code" %)
109 109  (((
110 -(% class="cm" style="color: rgb(153,153,136);" %)/~*~* * Route the edges that are connected with the children of the given node. * * @param parentNode the parent node of the input graph */(% class="kd" %)public(% class="kt" style="color: rgb(68,85,136);" %)void(% class="nf" style="color: rgb(153,0,0);" %)routeEdges(% class="o" %)((% class="kd" %)final(% class="o" %)){().(% class="na" style="color: rgb(0,128,128);" %)begin(% class="o" %)((% class="s" style="color: rgb(187,136,68);" %)"Edge Routing"(% class="o" %),(% class="mi" style="color: rgb(0,153,153);" %)1(% class="o" %));().(% class="na" style="color: rgb(0,128,128);" %)done(% class="o" %)();}
111 111  
112 -{{{
113 - KNode parentNode
114 - getMonitor
115 -
116 - getMonitor
117 -
118 -}}}
111 +\\\\\\\\\\\\\\
112 +
113 +{{{ /** * Route the edges that are connected with the children of the given node. * @param parentNode the parent node of the input graph */ public void routeEdges(final KNode parentNode) { getMonitor().begin("Edge Routing", 1); getMonitor().done(); }}}}
119 119  )))
120 -1. Add the following code to the end of the doLayout method in your layout provider:(% class="code" %)
115 +1. Add the following code to the end of the {{code language="none"}}doLayout{{/code}} method in your layout provider:(% class="code" %)
121 121  (((
122 -(% class="o" %)=(% class="k" %)new(% class="o" %)();.(% class="na" style="color: rgb(0,128,128);" %)reset(% class="o" %)(.(% class="na" style="color: rgb(0,128,128);" %)subTask(% class="o" %)((% class="mi" style="color: rgb(0,153,153);" %)1(% class="o" %)));.(% class="na" style="color: rgb(0,128,128);" %)routeEdges(% class="o" %)();
117 +(% class="o" %)=(% class="k" %)new(% class="o" %)();.(% class="na" style="color: rgb(0,128,128);" %)routeEdges(% class="o" %)();
123 123  
124 124  {{{ EdgeRouter edgeRouter EdgeRouter
125 - edgeRouterprogressMonitor
126 126   edgeRouterlayoutNode
127 127  }}}
128 128  )))
129 129  1. (((
130 -Implement the routeEdges method:
124 +Implement the {{code language="none"}}routeEdges{{/code}} method:
131 131  * Each edge shall be drawn with three line segments: one vertical segment starting below the source node, one horizonzal segment, and another vertical segment ending below the target node.
132 -* The horizontal segments of two different edges shall not have the same y-coordinate; for consecutive edges, the distance between their horizontal segments shall equal objectSpacing
133 -* See the attached image [[test-drawing.png>>url:http://trac.rtsys.informatik.uni-kiel.de/trac/10ss-layout/attachment/wiki/Exercises/Introduction/test-drawing.png||title="Attachment 'test-drawing.png' in Exercises/Introduction" shape="rect" class="attachment"]](% class="noprint" %) [[~[~[image:url:http://trac.rtsys.informatik.uni-kiel.de/trac/10ss-layout/chrome/common/download.png~]~]>>url:http://trac.rtsys.informatik.uni-kiel.de/trac/10ss-layout/raw-attachment/wiki/Exercises/Introduction/test-drawing.png||title="Download" shape="rect" class="trac-rawlink"]](%%) for an example
134 -* Find the edges using [[(% class="icon" %) (%%)getOutgoingEdges()>>url:http://rtsys.informatik.uni-kiel.de/~~kieler/doc/de/cau/cs/kieler/core/kgraph/KNode.html#getOutgoingEdges()||shape="rect" class="ext-link"]] or [[(% class="icon" %) (%%)getIncomingEdges()>>url:http://rtsys.informatik.uni-kiel.de/~~kieler/doc/de/cau/cs/kieler/core/kgraph/KNode.html#getIncomingEdges()||shape="rect" class="ext-link"]] on a node
126 +* The horizontal segments of two different edges shall not have the same y-coordinate; for consecutive edges, the distance between their horizontal segments shall equal {{code language="none"}}objectSpacing{{/code}}.
127 +* See the attached image [[attach:test-drawing.png]] for an example.
128 +* Find the edges using {{code language="none"}}getOutgoingEdges(){{/code}} or {{code language="none"}}getIncomingEdges(){{/code}} on a node.
135 135  * Get the edge layout of an edge to set bend points using this code:(% class="code" %)
136 136  (((
137 137  (% class="o" %)=.(% class="na" style="color: rgb(0,128,128);" %)getData(% class="o" %)(.(% class="na" style="color: rgb(0,128,128);" %)class(% class="o" %));
... ... @@ -146,8 +146,8 @@
146 146  {{{ KPoint point KLayoutDataFactory
147 147  }}}
148 148  )))
149 -* Use the [[(% class="icon" %) (%%)getBendPoints()>>url:http://rtsys.informatik.uni-kiel.de/~~kieler/doc/de/cau/cs/kieler/kiml/layout/klayoutdata/KEdgeLayout.html#getBendPoints()||shape="rect" class="ext-link"]] list on the edgeLayout to add bend points (clear the list first to remove points from the previous layout)
150 -* Set the values of the points returned by [[(% class="icon" %) (%%)getSourcePoint()>>url:http://rtsys.informatik.uni-kiel.de/~~kieler/doc/de/cau/cs/kieler/kiml/layout/klayoutdata/KEdgeLayout.html#getSourcePoint()||shape="rect" class="ext-link"]] and [[(% class="icon" %) (%%)getTargetPoint()>>url:http://rtsys.informatik.uni-kiel.de/~~kieler/doc/de/cau/cs/kieler/kiml/layout/klayoutdata/KEdgeLayout.html#getTargetPoint()||shape="rect" class="ext-link"]] according to the positions where the edge leaves its source node and reches its target node
143 +* Use the {{code language="none"}}getBendPoints(){{/code}} list on the {{code language="none"}}edgeLayout{{/code}} to add bend points (clear the list first to remove points from the previous layout).
144 +* Set the values of the points returned by {{code language="none"}}getSourcePoint(){{/code}} and {{code language="none"}}getTargetPoint(){{/code}} according to the positions where the edge leaves its source node and reches its target node.
151 151  )))
152 152  )))
153 153  1. Use your previous run configuration to test the edge router.
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -5505223
1 +6160455
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/SS13LayPract/pages/5505223/KIML
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/SS13LayPract/pages/6160455/KIML

Navigation

Quick Links

KIELER on GitHub
RTSYS Homepage