Summary

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

Details

Page properties

Content

...	...	@@ -1,0 +1,50 @@
	1	+
	2	+
	3	+= Preliminaries =
	4	+
	5	+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.
	6	+
	7	+== Required Software ==
	8	+
	9	+Install [[Eclipse>>url:http://eclipse.org/downloads||rel="nofollow" shape="rect" class="external-link"]]. For what we do, we recommend installing the Eclipse Modeling Tools.
	10	+
	11	+== Finding Documentation ==
	12	+
	13	+[[doc:Finding Documentation]]
	14	+
	15	+{{excerpt-include nopanel="true"/}}
	16	+
	17	+
	18	+
	19	+= Your First Steps with Eclipse =
	20	+
	21	+== Starting Eclipse ==
	22	+
	23	+1. Eclipse uses workspaces to store, for instance, user preferences. Upon the first start of eclipse you will be asked to specify a location. Select one as you like.
	24	+[[image:attach:workspace.jpg]]
	25	+1. Switch to the workbench, you should see something like this
	26	+[[image:attach:wb.jpg]]
	27	+
	28	+== Importing Existing Plug-ins ==
	29	+
	30	+1. [[Download >>url:https://git.rtsys.informatik.uni-kiel.de/plugins/servlet/archive/projects/MISC/repos/tutorials?at=refs%2Fheads%2Fmaster||shape="rect"]]the zip file with all our prepared tutorial plugins from our Stash. Unzip the file.
	31	+1. Open the context menu within the //Package-Explorer// (on the very left, right-click the empty space).
	32	+1. Select //Import//. Then chose //General > Existing Projects into Workspace//.
	33	+1. Browse to the location where you unzipped the downloaded plug-ins. Check the checkbox in front of the {{code language="none"}}de.cau.cs.kieler.tutorials.plugins.shouter{{/code}} plug-in and press //Finish.
	34	+[[image:attach:import.jpg]]
	35	+//
	36	+
	37	+== Creating Your First Plug-in ==
	38	+
	39	+1. Open the context menu within the //Package-Explorer// (on the very left, right-click the empty space).
	40	+1. //New// -> //Project...//
	41	+1. In the project wizard, choose //Plug-in Project// and click //Next//.
	42	+1. As the project name, enter {{code language="none"}}de.cau.cs.rtprak.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.rtprak.login.simple{{/code}}). Click //Next//.
	43	+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...)
	44	+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//.)
	45	+
	46	+
	47	+
	48	+Extension Points
	49	+
	50	+For the final part of the tutorial, we will now use the extension point mechanism of Eclipse to add some behavior to our Turing Machines. An //extension point// is basically a well-defined point where other plug-ins can register to add functionality. The extension point is basically defined by an XML Schema file that defines an interface; other plug-ins may access this interface using XML code in their {{code language="none"}}plugin.xml{{/code}} file, so-called //extensions//. Our extension point will provide an interface for classes that define behavior of a Turing Machine, and we will call them head controllers (programs that control the tape head).

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-10751594
	1	+10751601

URL

...	...	@@ -1,1 +1,1 @@
1		-https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/TUT/pages/10751594/Eclipse Plug-ins
	1	+https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/TUT/pages/10751601/Eclipse Plug-ins