Difference between revisions of "Visible plugin (extension point)"
From BioUML platform
Tagir Valeev (Talk | contribs) |
Tagir Valeev (Talk | contribs) (+registry) |
||
| Line 1: | Line 1: | ||
| − | {{Extension point|visiblePlugin|ru.biosoft.workbench}} | + | {{Extension point|visiblePlugin|ru.biosoft.workbench|registry=ru.biosoft.plugins.Plugins}} |
;Applicable for | ;Applicable for | ||
:[[BioUML workbench]] | :[[BioUML workbench]] | ||
Latest revision as of 16:54, 13 May 2013
- Identifier
- ru.biosoft.workbench.visiblePlugin
- Plugin
- ru.biosoft.workbench
- Registry
Plugins- Applicable for
- BioUML workbench
[edit] Description
BioUML workbench provides special tab where 'visible' plug-ins will be shown. For this purpose any plug-in can provide one ore more visible plug-in extensions.
There is special utility class VisiblePlugin from which other visible plug-ins can be inherited.
[edit] Configuration Markup
<!ELEMENT visiblePlugin>
<!ATTLIST visiblePlugin
name CDATA #REQUIRED
class CDATA #REQUIRED
displayName CDATA #IMPLIED
description CDATA
>
- name
- a unique name of plug-in.
- class
- the fully-qualified name of a class which implements
DataCollection. - displayName
- a plug-in title as it will be shown in plug-ins tab.
- description
- a plug-in description.
Note: some other valid properties from DataCollection and its ancestor can be used if necessary.
[edit] Examples
<extension point="ru.biosoft.workbench.visiblePlugin">
<visiblePlugin
name="SBW" class="biouml.plugins.sbw.SbwVisiblePlugin"
displayName="Systems Biology Workbench"
description="%sbw.descr"
/>
</extension>
[edit] API Information
The value of the class attribute must represent an implementor of VisiblePlugin.
