Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Parent

...	...	@@ -1,1 +1,1 @@
1		-SS13LayPract.Layout Practical (summer term 2013).Tutorials.WebHome
	1	+Projects.Layout Practical (summer term 2013).Tutorials.WebHome

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.cds
	1	+XWiki.stu230980

Content

...	...	@@ -32,7 +32,7 @@
32	32	* [[Java Platform, Standard Edition 6 API Specification>>url:http://download.oracle.com/javase/6/docs/api/||shape="rect"]]
33	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	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:\\
	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	36	** Programmer's Guide
37	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	38	** References -> API Reference
...	...	@@ -50,7 +50,7 @@
50	50
51	51	== Preparing the Repository ==
52	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:
	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	54
55	55	1. Open a console window and navigate to an empty directory that the repository should be placed in.
56	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)
...	...	@@ -80,9 +80,9 @@
80	80
81	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	82
83		-{{note}}
	83	+{{info}}
84	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		-{{/note}}
	85	+{{/info}}
86	86
87	87	== Setting Up Your Workspace ==
88	88
...	...	@@ -95,7 +95,7 @@
95	95	1. Add the KIML repository.
96	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	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.\\
	98	+1. Import the following plug-ins. This consitutes a basic configuration for the development of layout algorithms.
99	99	1*. de.cau.cs.kieler.core
100	100	1*. de.cau.cs.kieler.core.kgraph
101	101	1*. de.cau.cs.kieler.kiml
...	...	@@ -103,7 +103,7 @@
103	103	1*. de.cau.cs.kieler.kiml.service
104	104	1*. de.cau.cs.kieler.kiml.ui
105	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.\\
	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	107	1*. de.cau.cs.kieler.core.annotations
108	108	1*. de.cau.cs.kieler.core.kgraph.edit
109	109	1*. de.cau.cs.kieler.core.kivi
...	...	@@ -139,7 +139,7 @@
139	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	140
141	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:\\
	142	+1. Add dependencies to the following plug-ins:
143	143	1*. {{code language="none"}}de.cau.cs.kieler.core{{/code}}
144	144	1*. {{code language="none"}}de.cau.cs.kieler.core.kgraph{{/code}}
145	145	1*. {{code language="none"}}de.cau.cs.kieler.kiml{{/code}}
...	...	@@ -204,8 +204,8 @@
204	204	nodeLayout.setYpos(y);
205	205	{{/code}}
206	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}}.
	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	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	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	211	{{/info}}