Skip to Content
Last modified by cds on 2025/01/30 12:03
From version 4.1
edited by cds
on 2012/10/19 15:31
Change comment: There is no comment for this version
To version 5.1
edited by cds
on 2012/10/19 15:43
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -65,10 +65,20 @@
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 67  
68 -
68 +== Create the Main Editor Class ==
69 69  
70 -
70 +We will now create the class that implements the simple text editor. There won't be any programming involved here since we're lazy; instead, we will just inherit from an existing simple text editor.
71 71  
72 +1. //New// -> //Class//.
73 +1. Package: {{code language="none"}}de.cau.cs.rtprakt.login.simple.editors{{/code}}. Name: {{code language="none"}}SimpleEditorPart{{/code}}. Superclass: {{code language="none"}}org.eclipse.ui.editors.text.TextEditor{{/code}}. Click //Finish//.
74 +
75 +== Register the Editor ==
76 +
77 +For the editor to be available inside Eclipse, we will have to register it by adding an extension to an extension point.
78 +
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 +1. Open the //Plug-in Manifest Editor// again and switch to the //Extensions// tab.
81 +
72 72  
73 73  
74 74  
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -2982245
1 +2982247
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/WS12EclPract/pages/2982245/The Plugin Architecture of Eclipse
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/WS12EclPract/pages/2982247/The Plugin Architecture of Eclipse