Wiki source code of KIML
Last modified by Richard Kreissig on 2025/01/30 12:04
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | Welcome to the second tutorial! We will work our way through installing a proper Eclipse setup and developing a first very basic layout algorithm. The layout algorithm will integrate with KIML (KIELER Infrastructure for Meta-Layout), our very own framework that connects graphical editors with layout algorithms. Once you're finished, you should be able to create new Eclipse plug-ins and know how to write layout algorithms for KIML. And you should have a running Eclipse-based application that should look something like this: | ||
| 2 | |||
| 3 | [[image:attach:le_app_formidable.png]] | ||
| 4 | |||
| 5 | |||
| 6 | |||
| 7 | {{toc/}} | ||
| 8 | |||
| 9 | = Preliminaries = | ||
| 10 | |||
| 11 | There's a few things to do before we dive into the tutorial itself. For example, to do Eclipse programming, you will have to get your hands on an Eclipse installation first. Read through the following sections to get ready for the tutorial tasks. | ||
| 12 | |||
| 13 | == Required Software == | ||
| 14 | |||
| 15 | For this tutorial, we need you to have Eclipse and Git installed: | ||
| 16 | |||
| 17 | 1. Install Eclipse. For what we do, we recommend installing the Eclipse Modeling Tools, with a few extras. Our [[Wiki page on getting Eclipse>>doc:KIELER.Getting Eclipse]] has the details: simply follow the instructions for downloading and installing Eclipse and you should be set. | ||
| 18 | 1. You should already have obtained a working Git installation for the first tutorial. | ||
| 19 | |||
| 20 | == General Remarks == | ||
| 21 | |||
| 22 | Over the course of this tutorial, you will be writing a bit of code. Here's a few rules we ask you to follow: | ||
| 23 | |||
| 24 | * All the Java code you write as part of tutorials should be in packages with the prefix {{code language="none"}}de.cau.cs.rtprak.login.tutorialN{{/code}}, where {{code language="none"}}login{{/code}} is your login name as used for your email address at the institute. This rule will apply to all tutorials – once we start with the actual practical projects, we will choose more meaningful package name. | ||
| 25 | * All Java classes, fields, and methods should be thoroughly documented with the standard [[Javadoc>>url:http://download.oracle.com/javase/1.5.0/docs/tooldocs/windows/javadoc.html#javadoctags||shape="rect"]] comment format. Javadoc comments are well supported by Eclipse through code completion, syntax highlighting, and further features that help you. The code inside your methods should also be well commented. Try to think about what kinds of information would help someone unfamiliar with your code understand it. | ||
| 26 | * During this tutorial, we will be using Git mostly from the command line instead of using Eclipse's built-in Git support. This is because we've found Eclipse's Git support to be too unstable and buggy for us to trust it completely. | ||
| 27 | |||
| 28 | == Finding Documentation == | ||
| 29 | |||
| 30 | During the tutorial, we will cover each topic only briefly, so it is always a good idea to find more information online. Here's some more resources that will prove helpful: | ||
| 31 | |||
| 32 | * [[Java Platform, Standard Edition 6 API Specification>>url:http://download.oracle.com/javase/6/docs/api/||shape="rect"]] | ||
| 33 | As Java programmers, you will already know this one, but it's so important and helpful that it's worth repeating. The API documentation contains just about everything you need to know about the API provided by Java6. | ||
| 34 | * [[Eclipse Help System>>url:http://help.eclipse.org/juno/index.jsp||shape="rect"]] | ||
| 35 | Eclipse comes with its own help system that contains a wealth of information. You will be spending most of your time in the //Platform Plug-in Developer Guide//, which contains the following three important sections: | ||
| 36 | ** Programmer's Guide | ||
| 37 | When you encounter a new topic, such as SWT or JFace, the Programmer's Guide often contains helpful articles to give you a first overview. Recommended reading. | ||
| 38 | ** References -> API Reference | ||
| 39 | One of the two most important parts of the Eclipse Help System, the API Reference contains the Javadoc documentation of all Eclipse framework classes. Extremely helpful. | ||
| 40 | ** References -> Extension Points Reference | ||
| 41 | The other of the two most important parts of the Eclipse Help System, the Extension Point Reference lists all extension points of the Eclipse framework along with information about what they are and how to use them. Also extremely helpful. | ||
| 42 | * [[Eclipsepedia>>url:http://wiki.eclipse.org/Main_Page||shape="rect"]] | ||
| 43 | The official Eclipse Wiki. Contains a wealth of information on Eclipse programming. | ||
| 44 | * [[Eclipse Resources>>url:http://www.eclipse.org/resources/||shape="rect"]] | ||
| 45 | Provides forums, tutorials, articles, presentations, etc. on Eclipse and Eclipse-related topics. | ||
| 46 | |||
| 47 | You will find that despite of all of these resources Eclipse is still not as well commented and documented as we'd like it to be. Finding out how stuff works in the world of Eclipse can thus sometimes be a challenge. However, this does not only apply to you, but also to many people who are conveniently connected by something called //The Internet//. It should go without saying that if all else fails, [[Google>>url:http://www.google.de||shape="rect"]] often turns up great tutorials or solutions to problems you may run into. And if it doesn't, Miro and I will be happy to help you as well. | ||
| 48 | |||
| 49 | As far as KIML and layout algorithms are concerned, you can always refer to our Wiki which has a section about [[KIML and the KIELER layout projects>>doc:KIELER.Eclipse Layout Kernel (ELK)]]. The documentation is not complete, however, so feel free to ask Miro or Christoph Daniel for help if you have questions that the documentation fails to answer. | ||
| 50 | |||
| 51 | == Preparing the Repository == | ||
| 52 | |||
| 53 | We have created a Git repository for everyone to do his tutorials in. You can access the repository online through our Stash tool [[over here>>url:http://git.rtsys.informatik.uni-kiel.de:7990/projects/PRAK/repos/12ws-eclipse-tutorials/browse||shape="rect"]]. (% style="font-size:10.0pt; line-height:13.0pt" %)Clone that repository: | ||
| 54 | |||
| 55 | 1. Open a console window and navigate to an empty directory that the repository should be placed in. | ||
| 56 | 1. Enter the command [[ssh:~~/~~/git@git.rtsys.informatik.uni-kiel.de:7999/PRAK/13ss-layout-tutorials.git>>url:ssh://git@git.rtsys.informatik.uni-kiel.de:7999/PRAK/13ss-layout-tutorials.git||shape="rect"]]{{code language="none"}}git clone .{{/code}} (including the final dot, which tells git to clone the repository into the current directory instead of a subdirectory) | ||
| 57 | 1. You should now have a clone of the repository in the current directory. | ||
| 58 | |||
| 59 | You will use this repository for all your tutorial work, along with everyone else. To make sure that you don't interfere with each other, everyone will work on a different branch. This is not exactly how people usually use Git, but goes to demonstrate Git's flexibility... Add a branch for you to work in: | ||
| 60 | |||
| 61 | 1. Enter {{code language="none"}}git checkout -b login_name{{/code}} | ||
| 62 | |||
| 63 | You have just added and checked out a new branch. Everything you commit will go to this branch. To push your local commits to the server (which you will need to do so we can access your results), do the following: | ||
| 64 | |||
| 65 | 1. Enter {{code language="none"}}git push origin login_name{{/code}} | ||
| 66 | |||
| 67 | You would usually have to enter {{code language="none"}}git pull{{/code}} first, but since nobody will mess with your branch anyway this won't be necessary. By the way, you only need to mention {{code language="none"}}origin login_name{{/code}} with the first {{code language="none"}}git push{{/code}}, since Git doesn't know where to push the branch yet. After the first time, Git remembers the information and it will be enough to just enter {{code language="none"}}git push{{/code}}. | ||
| 68 | |||
| 69 | == Finding the KIML Sources == | ||
| 70 | |||
| 71 | If you want to develop a layout algorithm using KIML, you will have to get your hands at the KIML source code first. Of course, the code is available through a Git repository. | ||
| 72 | |||
| 73 | 1. Open a console window and navigate to an empty directory that the repository should be placed in. | ||
| 74 | 1. Enter the command [[ssh:~~/~~/git@git.rtsys.informatik.uni-kiel.de:7999/KIELER/pragmatics.git>>url:ssh://git@git.rtsys.informatik.uni-kiel.de:7999/KIELER/pragmatics.git||shape="rect"]]{{code language="none"}}git clone .{{/code}} | ||
| 75 | 1. You should now have a clone of the repository in the current directory. | ||
| 76 | |||
| 77 | KIML is implemented as an Eclipse plug-in that you will have to import into your Eclipse workspace. We won't do this now; it will be one of the first steps in the development of your layout algorithm. | ||
| 78 | |||
| 79 | = Developing Your First Layout Algorithm = | ||
| 80 | |||
| 81 | Now that the preliminaries are out of the way, it's time to develop your first layout algorithm! It will, however, be a very simple one. This tutorial focuses on creating Eclipse plug-ins and on learning how to develop with KIML; thinking of and implementing cool layout algorithms is what the rest of the practical will focus on, and that is where the fun will be had! | ||
| 82 | |||
| 83 | {{info}} | ||
| 84 | Remember to replace each occurrence of {{code language="none"}}login_name{{/code}} with your own login name (e.g. {{code language="none"}}msp{{/code}}), and each occurrence of {{code language="none"}}Login_name{{/code}} with your capitalized login name (e.g. {{code language="none"}}Msp{{/code}}). | ||
| 85 | {{/info}} | ||
| 86 | |||
| 87 | == Setting Up Your Workspace == | ||
| 88 | |||
| 89 | You will start by importing the plug-ins necessary to program with KIML. | ||
| 90 | |||
| 91 | 1. Start Eclipse and create a new workspace. | ||
| 92 | 1. Setup your workspace as explained in [[this guide>>doc:KIELER.Configuring Eclipse]]. | ||
| 93 | 1. We will now make the two local clones of our Git repositories known to Eclipse. To that end, open the //Git Repository Exploring// perspective through //Window// -> //Open Perspective// -> //Other//. | ||
| 94 | 1. Click on //Add an existing local Git repository// and choose the location of the tutorial repository. Note that when you open the repository entry, the branch you previously checked out is marked as the current branch under //Branches// -> //Local//. | ||
| 95 | 1. Add the KIML repository. | ||
| 96 | 1. We will now import the projects required for KIML development to your workspace. Right-click on the KIML repository and choose //Import Projects//. | ||
| 97 | 1. Choose //Import existing projects//, and select the //plugins// folder from the //Working Directory//. Then click //Next//. | ||
| 98 | 1. Import the following plug-ins. This consitutes a basic configuration for the development of layout algorithms. | ||
| 99 | 1*. de.cau.cs.kieler.core | ||
| 100 | 1*. de.cau.cs.kieler.core.kgraph | ||
| 101 | 1*. de.cau.cs.kieler.kiml | ||
| 102 | 1*. de.cau.cs.kieler.kiml.gmf | ||
| 103 | 1*. de.cau.cs.kieler.kiml.service | ||
| 104 | 1*. de.cau.cs.kieler.kiml.ui | ||
| 105 | 1*. de.cau.cs.kieler.klay.layered | ||
| 106 | 1. To actually test your layout algorithms, you will need some kind of simple graph editor. The following plug-ins will add our KEG editor to your installation, which is just that. | ||
| 107 | 1*. de.cau.cs.kieler.core.annotations | ||
| 108 | 1*. de.cau.cs.kieler.core.kgraph.edit | ||
| 109 | 1*. de.cau.cs.kieler.core.kivi | ||
| 110 | 1*. de.cau.cs.kieler.core.model | ||
| 111 | 1*. de.cau.cs.kieler.core.model.gmf | ||
| 112 | 1*. de.cau.cs.kieler.core.ui | ||
| 113 | 1*. de.cau.cs.kieler.karma | ||
| 114 | 1*. de.cau.cs.kieler.keg | ||
| 115 | 1*. de.cau.cs.kieler.keg.diagram | ||
| 116 | 1*. de.cau.cs.kieler.keg.diagram.custom | ||
| 117 | 1*. de.cau.cs.kieler.keg.edit | ||
| 118 | |||
| 119 | == Adding a New Plug-in == | ||
| 120 | |||
| 121 | We need to create a new plug-in to implement the layout algorithm in. Switch back to the Java or Plug-in Development perspective and follow these steps: | ||
| 122 | |||
| 123 | 1. Click //File// > //New// > //Other...// > //Plug-in Development// > //Plug-in Project//. | ||
| 124 | 1. Enter {{code language="none"}}de.cau.cs.rtprak.login_name.tutorial2{{/code}} as the project name. Uncheck //Use default location// and use {{code language="none"}}tutorial_repository_path/de.cau.cs.rtprak.login_name.tutorial2{{/code}} as the location. Click //Next//. | ||
| 125 | 1. Set the version to {{code language="none"}}0.1.0.qualifier{{/code}}, vendor to {{code language="none"}}Christian-Albrechts-Universität zu Kiel{{/code}}, and execution environment to //J2SE-1.5//. (do this for all plug-ins that you create!) | ||
| 126 | 1. Uncheck all checkboxes in the //Options// group and click //Finish//. | ||
| 127 | 1. If Eclipse asks you whether the //Plug-in Development// perspective should be opened, choose either //Yes// or //No//. It doesn't make much of a difference anyway. | ||
| 128 | |||
| 129 | You should now commit your new, empty project to the Git repository. We will do that from within Eclipse. | ||
| 130 | |||
| 131 | 1. Right-click your project in the //Package Explorer// and click //Team// > //Share Project...// | ||
| 132 | 1. As the repository type, select //Git// and click //Next//. | ||
| 133 | 1. Tell Eclipse what repository to add the project to. The repository you placed the project in is already preselected. Simply click //Finish//. | ||
| 134 | 1. Since Git support is now enabled for the project, right-click it again and click //Team// > //Commit...// | ||
| 135 | 1. Select all files, enter a (meaningful) commit message, and click //Commit//. | ||
| 136 | |||
| 137 | == Writing the Layout Algorithm == | ||
| 138 | |||
| 139 | When writing our layout algorithm, we are going to need to be able to access code defined in several other plug-ins. To do that, we need to add dependencies to those plug-ins: | ||
| 140 | |||
| 141 | 1. In your new plug-in, open the file {{code language="none"}}META-INF/MANIFEST.MF{{/code}}. The plug-in manifest editor will open. Open its //Dependencies// tab. | ||
| 142 | 1. Add dependencies to the following plug-ins: | ||
| 143 | 1*. {{code language="none"}}de.cau.cs.kieler.core{{/code}} | ||
| 144 | 1*. {{code language="none"}}de.cau.cs.kieler.core.kgraph{{/code}} | ||
| 145 | 1*. {{code language="none"}}de.cau.cs.kieler.kiml{{/code}} | ||
| 146 | 1. Save the editor. | ||
| 147 | |||
| 148 | Layout algorithms interface with KIML by means of a layout provider class that has to be created and registered with KIML. | ||
| 149 | |||
| 150 | 1. Right-click the source folder of your plug-in and click //New// > //Class//. | ||
| 151 | 1. Set the package to {{code language="none"}}de.cau.cs.rtprak.login_name.tutorial2{{/code}}, enter {{code language="none"}}Login_nameLayoutProvider{{/code}} as the class name, and select {{code language="none"}}de.cau.cs.kieler.kiml.AbstractLayoutProvider{{/code}} as the superclass. (This will only be available through the //Browse// dialog if you have saved the plug-in manifest editor; if you haven't, Eclipse won't know about the new dependencies yet.) | ||
| 152 | 1. Select //Generate comments// and click //Finish//. | ||
| 153 | |||
| 154 | Implement the layout provider class: | ||
| 155 | |||
| 156 | 1. ((( | ||
| 157 | Add the following constants: | ||
| 158 | |||
| 159 | {{code language="java"}} | ||
| 160 | /** default value for spacing between nodes. */ | ||
| 161 | private static final float DEFAULT_SPACING = 15.0f; | ||
| 162 | {{/code}} | ||
| 163 | ))) | ||
| 164 | 1. ((( | ||
| 165 | Use the following code as the skeleton of the {{code language="none"}}doLayout(...){{/code}} method: | ||
| 166 | |||
| 167 | {{code language="java"}} | ||
| 168 | progressMonitor.begin("Login_name layouter", 1); | ||
| 169 | KShapeLayout parentLayout = parentNode.getData(KShapeLayout.class); | ||
| 170 | |||
| 171 | float objectSpacing = parentLayout.getProperty(LayoutOptions.SPACING); | ||
| 172 | if (objectSpacing < 0) { | ||
| 173 | objectSpacing = DEFAULT_SPACING; | ||
| 174 | } | ||
| 175 | |||
| 176 | float borderSpacing = parentLayout.getProperty(LayoutOptions.BORDER_SPACING); | ||
| 177 | if (borderSpacing < 0) { | ||
| 178 | borderSpacing = DEFAULT_SPACING; | ||
| 179 | } | ||
| 180 | |||
| 181 | // TODO: Insert actual layout code. | ||
| 182 | |||
| 183 | progressMonitor.done(); | ||
| 184 | {{/code}} | ||
| 185 | ))) | ||
| 186 | 1. It is now time to write the code that places the nodes.Your code should place them next to each other in a row, as seen in the screenshot at the beginning of the tutorial. | ||
| 187 | |||
| 188 | {{info title="Tips"}} | ||
| 189 | The following tips might come in handy... | ||
| 190 | |||
| 191 | * Read the documentation of the [[KGraph>>doc:KIELER.KGraph Meta Model]] and [[KLayoutData>>doc:KIELER.KLayoutData Meta Model]] meta models. The input to the layout algorithm is a {{code language="none"}}KNode{{/code}} that has child {{code language="none"}}KNode{{/code}}s for every node in the graph. Iterate over these nodes by iterating over the {{code language="none"}}getChildren(){{/code}} list of the {{code language="none"}}parentNode{{/code}} argument. | ||
| 192 | * ((( | ||
| 193 | Retrieve the size of a node and set its position later using the following code: | ||
| 194 | |||
| 195 | {{code language="java"}} | ||
| 196 | KShapeLayout nodeLayout = node.getData(KShapeLayout.class); | ||
| 197 | |||
| 198 | // Retrieving the size | ||
| 199 | float width = nodeLayout.getWidth(); | ||
| 200 | float height = nodeLayout.getHeight(); | ||
| 201 | |||
| 202 | // Setting the position | ||
| 203 | nodeLayout.setXpos(x); | ||
| 204 | nodeLayout.setYpos(y); | ||
| 205 | {{/code}} | ||
| 206 | ))) | ||
| 207 | * {{code language="none"}}objectSpacing{{/code}}is the spacing to be left between each pair of nodes. | ||
| 208 | * {{code language="none"}}borderSpacing{{/code}}is the spacing to be left to the borders of the drawing. The top left node's coordinates must therefore be at least {{code language="none"}}(borderSpacing, borderSpacing){{/code}}. | ||
| 209 | * At the end of the method, set the width and height of {{code language="none"}}parentLayout{{/code}} such that it is large enough to hold the whole drawing, including borders. | ||
| 210 | * A complete layout algorithm will of course also route the edges between the nodes. Ignore that for now – you will do this at a later step. | ||
| 211 | {{/info}} | ||
| 212 | |||
| 213 | Before you can test your layout code, you will have to register your new layout provider with KIML. | ||
| 214 | |||
| 215 | 1. Open the {{code language="none"}}META-INF/MANIFEST.MF{{/code}} file again and switch to the //Extensions// tab. | ||
| 216 | 1. Add an extension for {{code language="none"}}de.cau.cs.kieler.kiml.layout.layoutProviders{{/code}}. | ||
| 217 | 1. Right-click the extension and click //New// > //layoutAlgorithm//. | ||
| 218 | 1. Set the name to {{code language="none"}}Login_name Test Layouter{{/code}} and the class to your layout provider class name. | ||
| 219 | 1. Right-click the new //layoutAlgorithm// and click //New// > //knownOption//. Set option to {{code language="none"}}de.cau.cs.kieler.spacing{{/code}}. | ||
| 220 | 1. Add another //knownOption// for {{code language="none"}}de.cau.cs.kieler.borderSpacing{{/code}}. | ||
| 221 | 1. Save the editor. | ||
| 222 | |||
| 223 | We will now have to add a new run configuration that will start an Eclipse instance with your layout code loaded into the application, ready to be used. | ||
| 224 | |||
| 225 | 1. Click //Run// > //Debug Configurations...// | ||
| 226 | 1. Right-click //Eclipse Application// and click //New//. Set the configuration's name to {{code language="none"}}Layout Test{{/code}}. | ||
| 227 | 1. In the //Arguments// tab, make sure the the program arguments include {{code language="none"}}-debug{{/code}} and {{code language="none"}}-consoleLog{{/code}}. | ||
| 228 | 1. On the //Plug-ins// tab, set //Launch with// to //plug-ins selected below only//. Click //Deselect All//, check the //Workspace// item in the tree, and click //Add Required Plug-ins//. | ||
| 229 | 1. Click //Apply// to save your changes and then //Debug// to start an Eclipse instance to test with. | ||
| 230 | |||
| 231 | Test the layouter in your new Eclipse instance: | ||
| 232 | |||
| 233 | 1. Click //New// > //Project...// > //General// > //Project// and set the project name to something like {{code language="none"}}Test{{/code}}. | ||
| 234 | 1. Right-click the new project and click //New// > //Empty KEG Graph//. Enter a meaningful name and click //Finish//. | ||
| 235 | 1. Put a few nodes into the diagram. To properly test your code, you will want to vary the sizes of the nodes. It may also be a good idea to get into the habit of giving each node a different name, such as N1, N2, etc. This will help you later if you have to debug your algorithm. | ||
| 236 | 1. Open the //Layout// view through //Window// > //Show View// > //Other...// > //KIELER Layout// > //Layout//. | ||
| 237 | 1. With your KEG diagram selected, set the //Layout Algorithm// option in the //Layout// view to your new algorithm. | ||
| 238 | 1. Save your KEG diagram. | ||
| 239 | 1. Trigger automatic layout by clicking the layout button in the toolbar, or by hitting Ctrl+R L (first Ctrl+R, then L). | ||
| 240 | |||
| 241 | {{info title="Tip"}} | ||
| 242 | You can see the direct output of your algorithm and the time it took to run it through the //Layout Graph// and //Layout Time// views. The views are available through the {{code language="none"}}de.cau.cs.kieler.kiml.debug{{/code}} plug-in, which can be found in the plugins-dev folder of the KIML repository. You will learn more about debugging layout algorithms in a layout tutorial or presentation. | ||
| 243 | {{/info}} | ||
| 244 | |||
| 245 | Once you're satisfied with your node placement code, it's time to take care of edge routing. | ||
| 246 | |||
| 247 | 1. ((( | ||
| 248 | Add a new method that will implement the edge routing using the following skeleton code: | ||
| 249 | |||
| 250 | {{code language="java"}} | ||
| 251 | /** | ||
| 252 | * Routes the edges connecting the nodes in the given graph. | ||
| 253 | * | ||
| 254 | * @param parentNode the graph whose edges to route. | ||
| 255 | * @param yStart y coordinate of the start of the edge routing area. | ||
| 256 | * @param objectSpacing the object spacing. | ||
| 257 | * @return height used for edge routing. | ||
| 258 | */ | ||
| 259 | private float routeEdges(final KNode parentNode, final float yStart, final float objectSpacing) { | ||
| 260 | // TODO: Implement edge routing | ||
| 261 | |||
| 262 | return 0; | ||
| 263 | } | ||
| 264 | {{/code}} | ||
| 265 | ))) | ||
| 266 | 1. Add a call to {{code language="none"}}routeEdges(...){{/code}} in your {{code language="none"}}doLayout(...){{/code}} method and implement the latter. | ||
| 267 | |||
| 268 | {{info title="Tips"}} | ||
| 269 | Here's a few tips for implementing the edge routing: | ||
| 270 | |||
| 271 | * Each edge shall be drawn with three orthogonal line segments: one vertical segment below the start node, one vertical segment below the target node, and a horizontal segment that connects the two. | ||
| 272 | * The horizontal segments of two different edges shall not have the same y-coordinate. Two neighboring horizontal segments shall be placed at a distance of objectSpacing. | ||
| 273 | * See the screenshot at the top of the tutorial for an example. | ||
| 274 | * Find the edges in a graph by calling {{code language="none"}}getOutgoingEdges(){{/code}} or {{code language="none"}}getIncomingEdges(){{/code}} on the nodes. | ||
| 275 | * ((( | ||
| 276 | You can add bend points to edges through the edge's edge layout: | ||
| 277 | |||
| 278 | {{code language="java"}} | ||
| 279 | KEdgeLayout edgeLayout = edge.getData(KEdgeLayout.class); | ||
| 280 | KPoint bendPoint = KLayoutDataFactory.eINSTANCE.createKPoint(); | ||
| 281 | edgeLayout.getBendPoints().add(bendPoint); | ||
| 282 | {{/code}} | ||
| 283 | ))) | ||
| 284 | * You will want to clear the list of bend points of each edge layout before adding bend points to it. This will remove all bend points the edge had prior to invoking your layout algorithm. | ||
| 285 | * Set the values of the points returned by {{code language="none"}}getSourcePoint(){{/code}} and {{code language="none"}}getTargetPoint(){{/code}} according to the positions where an edge leaves its source node and reaches its target node. | ||
| 286 | * If you want, you can improve the edge routing code by allowing horizontal segments to share the same y-coordinate if that doesn't make them overlap. Your goal could be to produce an edge routing that uses as little space as possible. | ||
| 287 | * If that's not enough yet: can you find a way to find an order of the horizontal segments such that as few edge crossings as possible are produced? | ||
| 288 | {{/info}} | ||
| 289 | |||
| 290 | Once you're done implementing the edge routing code, test it by running your debug configuration again, as before. | ||
| 291 | |||
| 292 | == Before You Run Away... == | ||
| 293 | |||
| 294 | ...don't forget to commit your layout algorithm to your repository, and to push your commits to the tutorial repository on our server. If it's not there, we won't be able to see your work! | ||
| 295 | |||
| 296 |