Summary

• Page properties (1 modified, 0 added, 0 removed)
• Objects (1 modified, 0 added, 0 removed)
  • Confluence.Code.ConfluencePageClass[0]

Details

Page properties

Content

...	...	@@ -22,6 +22,7 @@
22	22	* All your Java code should be in packages with the prefix {{code language="none"}}de.cau.cs.rtprakt.login{{/code}}, where {{code language="none"}}login{{/code}} is your login name as used for your email address at the institute. From now on, this rule will apply to all tutorials. Once we start with the actual practical projects, we will choose another package name.
23	23	* All Java classes, fields, and methods should be thoroughly commented 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, providing code completion, syntax highlighting, and further features to 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.
24	24	* As you will already have noticed during the first tutorial, our tutorials use Turing machines as the underlying theme. This is partly because we're computer scientists and computer scientists are expected to choose computer sciency examples, but mostly because Turing machines work great as examples for the different kinds of topics we will be covering with you. You may thus want to take some time to read up again on the topic. [[Wikipedia>>url:http://en.wikipedia.org/wiki/Turing_machine||shape="rect"]] or the material of your Theoretical Computer Science lecture might be a great start.
	25	+* 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.
25	25
26	26	== Finding Documentation ==
27	27
...	...	@@ -43,3 +43,37 @@
43	43	Provides forums, tutorials, articles, presentations, etc. on Eclipse and Eclipse-related topics.
44	44
45	45	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.
	47	+
	48	+== Preparing the Repository ==
	49	+
	50	+{{warning title="ToDo"}}
	51	+Write this section.
	52	+{{/warning}}
	53	+
	54	+= Creating a Simple Text Editor =
	55	+
	56	+OK, with all the preliminaries out of the way let's get working. Fire up Eclipse, choose an empty workspace, close the Welcome panel it will present you with and follow the following steps.
	57	+
	58	+== Creating a New Plugin ==
	59	+
	60	+For our text editor to integrate into Eclipse, we need to create a plug-in project for it:
	61	+
	62	+1. //New// -> //Project...//
	63	+1. In the project wizard, choose //Plug-in Project// and click //Next//.
	64	+1. As the project name, enter {{code language="none"}}de.cau.cs.rtprakt.login.simple{{/code}}. Uncheck //Use default location// (which would put the project into your workspace), and put it into your local clone of the Git repository instead (the //Location// should read something like {{code language="none"}}/path/to/git/repository/de.cau.cs.rtprakt.login.simple{{/code}}). Click //Next//.
	65	+1. As the name, enter {{code language="none"}}Simple (login){{/code}}. Also, make sure that //Generate an activator// and //This plug-in will make contributions to the UI// are both checked. Click //Finish//. (Eclipse might ask you whether you want to switch to the //Plug-in Development Perspective//, which configures Eclipse to provide the views that are important for plug-in development. Choose //Yes//. Or //No//. It won't have a big influence on your future...)
	66	+1. Eclipse has now created your new plug-in and was nice enough to open the //Plug-in Manifest Editor//, which allows you to graphically edit two important files of your plugin: {{code language="none"}}plugin.xml{{/code}} and {{code language="none"}}META-INF/MANIFEST.MF{{/code}}. (By the way, this would be a great time to research the editor and the two files online.) Basically, those two files provide information that tell Eclipse what other plug-ins your plug-in needs and how it works together with other plug-ins by providing extensions and extension points. Our new plug-in will depend on two other plug-ins, so switch to the //Dependencies// tab of the editor and add dependencies to {{code language="none"}}org.eclipse.ui.editors{{/code}} and {{code language="none"}}org.eclipse.jface.text{{/code}}. Save the editor and close it. (You can always reopen it by opening one of the two mentioned files from the //Package Explorer//.)
	67	+
	68	+
	69	+
	70	+
	71	+
	72	+
	73	+
	74	+
	75	+
	76	+
	77	+
	78	+
	79	+
	80	+

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-2982241
	1	+2982245

URL

...	...	@@ -1,1 +1,1 @@
1		-https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/WS12EclPract/pages/2982241/The Plugin Architecture of Eclipse
	1	+https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/WS12EclPract/pages/2982245/The Plugin Architecture of Eclipse