PluginTypes - Revision history

TaniaTudorache at 06:09, May 24, 2016

2016-05-24T06:09:51Z

TaniaTudorache at 05:11, May 24, 2016

2016-05-24T05:11:10Z

TaniaTudorache at 03:50, May 24, 2016

2016-05-24T03:50:34Z

TaniaTudorache at 03:50, May 24, 2016

2016-05-24T03:50:19Z

Swartik: Fixed reference to wrong class

2011-04-04T20:11:43Z

Fixed reference to wrong class

Swartik: Grammar and typography fixes

2011-02-25T21:06:34Z

Grammar and typography fixes

Tredmond: /* Creating a tabbed view layout */

2011-02-16T01:04:46Z

‎Creating a tabbed view layout

Tredmond: /* Creating a tabbed view layout */

2011-02-16T01:04:32Z

‎Creating a tabbed view layout

Nickdrummond: /* ui.editor.description (from build 109) */ added indexing

2009-03-26T14:00:38Z

‎ui.editor.description (from build 109): added indexing

Nickdrummond: /* OWL Plugins */ added ui.editor.description

2009-02-26T16:05:58Z

‎OWL Plugins: added ui.editor.description

@@ Line 4: / Line 4: @@
 </div><br /><br />
-Back to [[Protege4DevDocs|Protege Developer Documentation]]
+'''Back to [[Main_Page#Developer_Documentation|Protege Developer Documentation]]'''
 __TOC__
@@ Line 265: / Line 265: @@
          <index value="B"/><!-- from build 110 -->
      </extension>

@@ Line 24: / Line 24: @@
 The most common plugin type – implements views (the building blocks of workspace tabs).
-Implementation of this plugin is demonstrated in the [http://www.co-ode.org/downloads/protege-x/plugin-code-example.php '''TabbedHierarchyView''' example].
+Implementation of this plugin is demonstrated in the [https://github.com/co-ode-owl-plugins/co-ode-owl-plugins/blob/master/taxonomy/src/main/java/org/coode/taxonomy/TabbedHierarchyView.java '''TabbedHierarchyView''' example].
 There are many abstract implementations of this plugin to use as a base, for example each entity type (Class, Property and Individual) has an abstract base.

@@ Line 5: / Line 5: @@
 Back to [[Protege4DevDocs|Protege Developer Documentation]]
 __TOC__
@@ Line 19: / Line 18: @@
 ==== ViewComponent ====

@@ Line 1: / Line 1: @@
 <div class="orangeBox">
-<span class="orangeBoxTitle">Protege 4 Plugin types</span><br /><br />
+<span class="orangeBoxTitle">Protege Plugin types</span><br /><br />
-This page summarises the default types of plugin that can be implemented for Protege 4.
+This page summarises the default types of plugin that can be implemented for Protege 4, 5 and newer.
 </div><br /><br />
-Back to [[Protege4DevDocs]]
+Back to [[Protege4DevDocs|Protege Developer Documentation]]
@@ Line 11: / Line 11: @@
 == Existing Plugin Types ==
-This is a snapshot of the existing types of plugins that can be added to Protege4.0.
+This is a snapshot of the existing types of plugins that can be added to Protege.
 The current set of plugin types can always be found in the code by looking at the plugin.xml file for the core.application and the owl bundles.
 Just look for the extension-points in these files – these point to the schemas that are used for describing each type of plugin.
@@ Line 80: / Line 80: @@
   <extension id="menu.PluginsMenuItem" point="org.protege.editor.core.application.EditorKitMenuAction">
          <name value="Protege-OWL plugins"/>
-         <toolTip value="Protege 4.0 OWL plugins"/>
+         <toolTip value="Protege plugins"/>
          <url value="http://protegewiki.stanford.edu/index.php/Protege-OWL_4.0"/>
          <path value="org.protege.editor.core.application.menu.HelpMenu/SlotF-B"/>
@@ Line 92: / Line 92: @@
 Create a panel that will be loaded into the preferences dialog.
-This should be for controlling a particular aspect of Protege4.0 in general or can be used as part of a bundle to control the behaviour of other plugins.
+This should be for controlling a particular aspect of Protege in general or can be used as part of a bundle to control the behaviour of other plugins.
 Preferences should be used to persist over sessions.
@@ Line 116: / Line 116: @@
 ===== Creating a tabbed view layout =====
 * First, create or decide on which views you wish to have on your tab - make sure these are all implemented
-* Open Protege 4.0
+* Open Protege
 * Create a new tab ('''Window | Create new tab...''')
 * Select your new tab and start customising it by adding views (see [[Protege4GettingStarted#Reconfigure_the_User_Interface|Reconfigure the user interface]])

@@ Line 98: / Line 98: @@
 The '''applyChanges()''' method should be used to update the appropriate values in Protege's '''PreferencesManager'''.
-* Implement: '''org.protege.editor.owl.ui.preferences.PreferencesPanel'''
+* Implement: '''org.protege.editor.owl.ui.preferences.OWLPreferencesPanel'''
 * Example: '''org.protege.editor.owl.ui.tree.OWLTreePreferencesPanel'''

@@ Line 13: / Line 13: @@
 This is a snapshot of the existing types of plugins that can be added to Protege4.0.
 The current set of plugin types can always be found in the code by looking at the plugin.xml file for the core.application and the owl bundles.
-Just look for the extension-points in these files - these point to the schemas that are used for describing each type of plugin.
+Just look for the extension-points in these files – these point to the schemas that are used for describing each type of plugin.
 Plenty of examples can be found in the plugin.xml files themselves.
@@ Line 24: / Line 24: @@
 <hr>
-The most common plugin type - implements views (the building blocks of workspace tabs).
+The most common plugin type – implements views (the building blocks of workspace tabs).
 Implementation of this plugin is demonstrated in the [http://www.co-ode.org/downloads/protege-x/plugin-code-example.php '''TabbedHierarchyView''' example].
@@ Line 109: / Line 109: @@
 Unless your tab requires some special handling for events or non-standard layout you will probably not need to implement a class for this plugin.
 You can just point the plugin.xml configuration to WorkspaceViewsTab (or OWLWorkspaceViewsTab) implementation and the rest of the plugin description
-should be enough to customise the tab - ie give it a name and point to a default layout (see below).
+should be enough to customise the tab – i.e., give it a name and point to a default layout (see below).
 * Implement: '''org.protege.editor.core.ui.workspace.WorkspaceTab'''

@@ Line 119: / Line 119: @@
 * Create a new tab ('''Window | Create new tab...''')
 * Select your new tab and start customising it by adding views (see [[Protege4GettingStarted#Reconfigure_the_User_Interface|Reconfigure the user interface]])
-* Select '''Tabs | Save current layout''' or quit Protege
+* Select '''Window | Save current layout''' or quit Protege
 * Find the new layout in the Protege installation directory ''Data/ViewConfigurations/viewconfig-custom-YOUR_TAB_NAME.xml''
 * Rename this without the ''custom'' and copy to somewhere in your plugin source like a ''resources/'' folder

@@ Line 245: / Line 245: @@
          <name value="Axioms by reference (select entities from the ontology)" />
          <class value="org.protege.editor.owl.ui.ontology.wizard.move.byreference.MoveAxiomsByReferenceKit" />
      </extension>