Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Platform UI/New Extension Point

< Platform UI
Revision as of 11:59, 3 April 2008 by Kim horne.ca.ibm.com (Talk | contribs) (New page: Things to do when creating a new extension point: * ensure that the schema file is documented. This includes documentation text for each element and attribute as well as content for eac...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Things to do when creating a new extension point:

* ensure that the schema file is documented.  This includes documentation text for each element and attribute as well as content for each of the tabs in the Overview page (Ie: the the Since tab, Examples tab, etc)
* ensure there are test cases 
* ensure that the extension response to dynamic plug-in loading.  Ie: when a plugin comes along that provides an extension of this type your code handles the addition (and possibly removal) gracefully.
* ensure that, wherever it is feasible, you use abstract classes rather than interfaces to describe the code that clients should subclass.  It is much easier to grow API from a class than an interface.
* add the extension to org.eclipse.platform.doc.isv/references/extension-points/index.html

Back to the top