Difference between revisions of "Plugin certification checklist"
| Line 1: | Line 1: | ||
== Major Checklist Items == | == Major Checklist Items == | ||
| + | * All interface components (buttons, lists, etc.) of a plugin should be fully functional. | ||
| + | * All components must have a full help section. | ||
| + | * Plugins should not include large datasets or example data unless totally necessary. Large extra data should be downloaded seperately to save CVS overhead and to allow for easy plugin updates. | ||
* Plugins should create dataset subnodes for their results so the user can see and navigate to the result. | * Plugins should create dataset subnodes for their results so the user can see and navigate to the result. | ||
* Plugins should specify what datasets they can accept and process through the use of the @AcceptTypes annotation. They should only specify datasets that they can properly support and then will only be visible when relevant to the current data loaded. | * Plugins should specify what datasets they can accept and process through the use of the @AcceptTypes annotation. They should only specify datasets that they can properly support and then will only be visible when relevant to the current data loaded. | ||
| + | * Plugins should only generate events necessary to their function. Unnecessary event generation can seriously impact application performance. | ||
| + | |||
== Minor Items == | == Minor Items == | ||
* Plugin should conform to look and feel guidelines, and should make use of standard button placements and layouts. | * Plugin should conform to look and feel guidelines, and should make use of standard button placements and layouts. | ||
Revision as of 15:33, 2 January 2006
Major Checklist Items
- All interface components (buttons, lists, etc.) of a plugin should be fully functional.
- All components must have a full help section.
- Plugins should not include large datasets or example data unless totally necessary. Large extra data should be downloaded seperately to save CVS overhead and to allow for easy plugin updates.
- Plugins should create dataset subnodes for their results so the user can see and navigate to the result.
- Plugins should specify what datasets they can accept and process through the use of the @AcceptTypes annotation. They should only specify datasets that they can properly support and then will only be visible when relevant to the current data loaded.
- Plugins should only generate events necessary to their function. Unnecessary event generation can seriously impact application performance.
Minor Items
- Plugin should conform to look and feel guidelines, and should make use of standard button placements and layouts.
