Difference between revisions of "Platform UI/New Extension Point"

From Eclipsepedia

Jump to: navigation, search
(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...)
 
m
 
Line 1: Line 1:
 
Things to do when creating a new extension point:
 
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 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 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 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.
+
* 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
+
* add the extension to org.eclipse.platform.doc.isv/references/extension-points/index.html

Latest revision as of 12:01, 3 April 2008

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