Changes for page The Plug-in Architecture of Eclipse

Last modified by cds on 2025/01/30 12:03

From version < 25.1 >

edited by cds
on 2012/10/24 17:49

To version < 23.1 >

edited by cds
on 2012/10/24 17:31

Change comment: There is no comment for this version

Raw
Rendered

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,9 +1,11 @@
++{{warning title="Warning"}}
++This tutorial isn't complete yet!
++{{/warning}}
++
  This tutorial will teach you the basics of writing plugins that run inside the Eclipse framework. You will learn about editors, views, and extension points by creating one of each yourself.
--You may want to download [[the slides>>attach:presentation.pdf]] of the presentation explaining the basic concepts you will explore in this tutorial.
--
  {{toc/}}
  = Preliminaries =
@@ -407,7 +407,7 @@
  We will now add a class that will be in charge of loading all extensions registered at our new extension point.
 . (((
--Add a class {{code language="none"}}HeadControllers{{/code}} to the package {{code language="none"}}de.cau.cs.rtprak.login.simple.controller{{/code}}. Add the following code, replacing {{code language="none"}}login{{/code}} with your login name in {{code language="none"}}EXTENSION_POINT_ID{{/code}} as usual:
++Add a class {{code language="none"}}HeadControllers{{/code}} to the package {{code language="none"}}de.cau.cs.rtprak.login.simple.controller{{/code}}. Add the following code:
  {{code language="java"}}
  /**
@@ -417,7 +417,7 @@
   */
  public class HeadControllers {
      /** Identifier of the extension point */
--    public final static String EXTENSION_POINT_ID = "de.cau.cs.rtprak.login.simple.headControllers";
++    public final static String EXTENSION_POINT_ID = "de.cau.cs.rtprak.groupx.simple.headControllers";
      /** The singleton instance of the {@code HeadControllers} class */
      public final static HeadControllers INSTANCE = new HeadControllers();
      /** list of head controller ids with associated names. */
@@ -550,51 +550,32 @@
 *. Set the current head position to 1.
 *. Refresh the table viewer with its {{code language="none"}}refresh(){{/code}} method.
--== Adding a Test Head Controller ==
++
--Before creating a proper head controller in another plug-in, we will add a test controller to check whether all this stuff works.
++
--1. (((
--Add a new class {{code language="none"}}NullController{{/code}} to the {{code language="none"}}de.cau.cs.rtprak.login.simple.controllers{{/code}} package:
++
--{{code language="java"}}
--/**
-- * Head controller that does nothing, for testing.
-- * @author msp
-- */
--public class NullController implements IHeadController {
--    /**
--     * {@inheritDoc}
--     */
--    public HeadCommand nextCommand(final char character) {
--        return new HeadCommand(Action.NULL, Direction.NONE, '_');
--    }
--
--    /**
--     * {@inheritDoc}
--     */
--    public void reset() {
--    }
--}
--{{/code}}
--)))
--1. Open the //Plugin Manifest Editor// and switch to the //Extensions// tab. Add your {{code language="none"}}de.cau.cs.rtprak.login.simple.headControllers{{/code}} extension point. Add a {{code language="none"}}controller{{/code}} element with ID {{code language="none"}}de.cau.cs.rtprak.login.simple.nullController{{/code}}, name {{code language="none"}}Null Controller{{/code}}, and class {{code language="none"}}de.cau.cs.rtprak.login.simple.controller.NullController{{/code}}.
--1. Start the application and observe how your program behaves if you change the action and direction in the {{code language="none"}}NullController{{/code}} class. You can actually change both while the application is running, but only if you have started it in the Debug mode. In that case, Eclipse will actually hot-swap your changes into the running application. Sorcery!
++
--== Implementing Your Own Head Controller ==
++
--We will now create a new plug-in with a new head controller:
++
--1. Create a new plug-in {{code language="none"}}de.cau.cs.rtprak.login.simple.extension{{/code}}. In the //Plugin Manifest Editor//, add {{code language="none"}}de.cau.cs.rtprak.login.simple{{/code}} to the dependencies of the new plug-in.
--1. Create a new class that implements {{code language="none"}}IHeadController{{/code}}:\\
--1*. Assuming that the initial head position is 1, the controller shall copy the input text infinitely often. So if the tape initially contains the word {{code language="none"}}hello{{/code}}, the controller shall generate {{code language="none"}}hellohellohellohe...{{/code}} .
--1*. Your class needs some private fields to store the internal state of the controller, and you may need some special character as marker. Imagine how a Turing Machine would do this.
--1*. It is not allowed to store data that can grow infinitely, since a Turing Machine may only have a finite number of states. This means that you may store single characters or numbers, but you must not store Strings, StringBuffers, arrays, lists, or sets.
--1. Register the new controller class using an extension in the new plug-in.
--1. Test your controller.
++
--= Congratulations! =
++
--Congratulations, you just made a big step towards understanding how Eclipse works. Plus, you've refreshed your knowledge on Turing Machines along the way. Eclipse is an industry standard technology, and having experience programming against it is a valuable skill for you.
++
--If you have any comments and suggestions for improvement concerning this tutorial, please don't hesitate to tell us about them!
++
++
++
++
++
++
++
++
++
++
++

Confluence.Code.ConfluencePageClass[0]

Id

@@ -1,1 +1,1 @@
--2982320
++2982314

URL

@@ -1,1 +1,1 @@
--https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/WS12EclPract/pages/2982320/The Plug-in Architecture of Eclipse
++https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/WS12EclPract/pages/2982314/The Plug-in Architecture of Eclipse

Changes for page The Plug-in Architecture of Eclipse

Summary

Details

Navigation

Quick Links