Creating a Simple Plug-in using PDE (II)
23 January 2008This post is in continuation of Creating a Simple Plug-in using PDE (I). Please do read that before this one.
The Overview page contains some general properties, such as the ID of your plug-in, its version, name, provider, plug-in class, and platform filter. It also provides links to pages for specifying plug-in content, its build configuration, as well as links for test-running and exporting the plug-in (all with brief descriptions). The ID is required and must uniquely identify your plug-in, globally. The Version is typically a three- or four-part, dot-separated version identifier (major.minor.service{.qualifier}). Plug-in versioning is documented in detail in your Platform Plug-in Developer Guide; in this exercise, you will settle for the default 1.0.0. The Name and Provider are optional and are only used as display labels in product configuration. The Class property is also optional, and for now it’ll suffice to say that it represents a singleton instance of the plug-in at run-time, typically used as a single point of access to various plug-in-specific data. In this example, the wizard generates a default implementation of this class for you, but you will not reference it from any code developed in this example. Platform filter can be used to restrict the plug-in’s platform applicability.
Related Posts:
- Creating a plug-in project (I)
- Creating a Simple Plug-in using PDE (I)
- Eclipse Plug-in Development Environment (II)
- PDE concepts (I)
- PDE Concepts (II)
- Creating a plug-in project (II)
- Eclipse Plug-in Development Environment (I)
- Plugin project - Dependencies page (II)
- Plug-in manifest editor
- Plugin project - Dependencies page (I)
Top Of Page | Trackback
If you found this page useful, consider linking to it. Simply copy and paste the code below into your web site.
It will look like this: Creating a Simple Plug-in using PDE (II)
