Summary

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

Details

Page properties

Content

...	...	@@ -64,6 +64,7 @@
64	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	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	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	+1. (% style="color: rgb(153,51,0);" %)**TODO: GIT PROJECT**
67	67
68	68	== Create the Main Editor Class ==
69	69
...	...	@@ -78,7 +78,24 @@
78	78
79	79	1. Copy [[the attached file>>attach:turing-file.gif]] to a new subfolder icons in the plug-in folder (right-click the plug-in folder in the //Package Explorer// and choose //New// -> //Folder...//). You can copy the file by importing it from inside Eclipse (//File// -> //Import...// -> //File System//) or by copying it from outside Eclipse and refreshing the plug-in project afterwards (right-click the plug-in folder in the //Package Explorer// and choose //Refresh).//
80	80	1. Open the //Plug-in Manifest Editor// again and switch to the //Extensions// tab.
	82	+1. Click //Add...//, choose the {{code language="none"}}org.eclipse.ui.editors{{/code}} extension point and click //Finish//.
	83	+1. The extension point is now shown in the list of extensions, along with an //editor// extension. Select that extension and edit its details using the fields on the right. Set the ID to {{code language="none"}}de.cau.cs.rtprakt.login.simple.editor{{/code}}, the name to {{code language="none"}}Simple Text Editor{{/code}}, the icon to {{code language="none"}}icons/turing-file.gif{{/code}}, the extensions to {{code language="none"}}simple{{/code}}, the class to {{code language="none"}}de.cau.cs.rtprakt.login.simple.editors.SimpleEditorPart{{/code}}, and the default to {{code language="none"}}true{{/code}}.
	84	+1. Save the manifest editor.
81	81
	86	+== Test the Editor ==
	87	+
	88	+It's time to test your new simple editor in a new Eclipse instance.
	89	+
	90	+1. Switch back to the //Overview// tab of the //Plug-in Manifest Editor//.
	91	+1. Click //Launch an Eclipse Application.//\\
	92	+1*. For future tests, you can now select //Eclipse Application// in the run menu.
	93	+1*. To enable debug mode for your test instances: open the //Run Configurations// dialog, select the //Arguments// tab of the //Eclipse Application// configuration, and add -debug -consoleLog as program arguments. This dumps all errors and exceptions to the console view, so you can directly see what went wrong.
	94	+1*. To improve performance, select only the plugins that are necessary: in the //Plug-ins// tab select //Launch with plug-ins selected below only//, deselect //Target Platform//, select //Workspace//, and then //Add Required Plug-ins//.\\
	95	+1**. Make sure that org.eclipse.ui.ide.application is also selected, else you won't be able to launch Eclipse.
	96	+1**. The requirements list needs to be updated when the dependencies of your plugins have changed; click //Add Required Plug-ins// again for updating.
	97	+1. In the new Eclipse instance, click //New -> Project...// -> //General// -> //Project//. Enter {{code language="none"}}test{{/code}} as the project name.
	98	+1. Right-click the new project and click //New// -> //File...// As the file name, enter {{code language="none"}}test.simple{{/code}}. This will create a new file with that name and open the file in your newly added text editor. (You can see that it is your editor by looking at the editor icon, which should look like the icon you downloaded and put into the icons folder.)
	99	+
82	82
83	83
84	84

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-2982247
	1	+2982252

URL

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