Protege5DevDocs - Revision history

TaniaTudorache at 06:19, May 24, 2016

2016-05-24T06:19:32Z

TaniaTudorache at 06:16, May 24, 2016

2016-05-24T06:16:38Z

TaniaTudorache at 06:02, May 24, 2016

2016-05-24T06:02:07Z

TaniaTudorache at 05:58, May 24, 2016

2016-05-24T05:58:14Z

TaniaTudorache at 05:56, May 24, 2016

2016-05-24T05:56:29Z

TaniaTudorache at 05:53, May 24, 2016

2016-05-24T05:53:20Z

TaniaTudorache at 05:51, May 24, 2016

2016-05-24T05:51:34Z

TaniaTudorache at 05:40, May 24, 2016

2016-05-24T05:40:44Z

TaniaTudorache at 05:39, May 24, 2016

2016-05-24T05:39:20Z

TaniaTudorache at 05:36, May 24, 2016

2016-05-24T05:36:27Z

← Older revision		Revision as of 06:19, May 24, 2016
Line 65:		Line 65:
	It is surprising how many people have written plugins for Protege that we just don't hear about.<br />		It is surprising how many people have written plugins for Protege that we just don't hear about.<br />
	If you wish to publish to the community, please see our notes on [[Protege4Contributing\|code contributions]].		If you wish to publish to the community, please see our notes on [[Protege4Contributing\|code contributions]].
		+
		+	== Getting help==
		+
		+	If you need additional support, please contact us via the [http://protege.stanford.edu/support.php protege-dev] mailing list. You need to be [https://mailman.stanford.edu/mailman/listinfo/protege-dev subscribed] in order to post to the list. In your post, please provide a detailed description of the problem, the steps to reproduce it, and any exception traces or logs that are relevant.

@@ Line 64: / Line 64: @@
 '''Please share.'''
 It is surprising how many people have written plugins for Protege that we just don't hear about.<br />
-If you wish to publish to the community, please see our notes on [[Protege4Contributing#Code_submissions|code contributions]].
+If you wish to publish to the community, please see our notes on [[Protege4Contributing|code contributions]].

@@ Line 1: / Line 1: @@
-= Protege Desktop 5.x Developer Documentation =
+<div class="orangeBox">
-This page is a top-level entry point for all '''developer documentation''' related to the Protege Desktop application, versions 5.0 and above.
+__TOC__
-=== Building ===
+== Building ==
-==== Accessing the source code ====
+=== Accessing the source code ===
 Protege Desktop is open source and the code is freely [http://github.com/protegeproject/protege available] on GitHub.  Use the following Git command to get a local copy:
@@ Line 16: / Line 18: @@
 The source code for many Protege Desktop plug-ins has also been made available on GitHub under the [https://github.com/protegeproject Protege Project organization].
-==== Building from source  ====
+=== Building from source  ===
 The instructions for building from source are available on [https://github.com/protegeproject/protege/wiki/Building-from-Source GitHub].
-==== Building with Eclipse and other IDEs ====
+=== Building with Eclipse and other IDEs ===
 We would welcome contributions from the community for setting up development environments other than Eclipse.
@@ Line 25: / Line 27: @@
-=== Protege APIs ===
+== Protege APIs ==
 The [[P4APIOverview|Protege API]] gives access to the ontology model and offers various utilities.
@@ Line 32: / Line 34: @@
-=== Developing a plugin ===
+== Developing a plugin ==
 Protege has been written specifically to be modular. It uses the [http://www.osgi.org/About/Technology OSGi framework] as a plugin infrastructure.
@@ Line 47: / Line 49: @@
-===Embedded OSGi===
+==Embedded OSGi==
 For people embedding Protege services inside a non-OSGi based applications, [[Embedding OSGi|here]] is a short example showing how this can work.
-=== Client-server ===
+== Client-server ==
 * [[Protege_5_Development_Environment|Setting up a development environment for the OWL Ontology Server]]
 * [[Protege_Server_design|OWL Ontology Server design]]
-=== Troubleshooting ===
+== Troubleshooting ==
 * [[SolvingClassLoaderProblems|Troubleshooting class loader issues]]
-=== Contributing ===
+== Contributing ==
 '''Please share.'''
 It is surprising how many people have written plugins for Protege that we just don't hear about.<br />
 If you wish to publish to the community, please see our notes on [[Protege4Contributing#Code_submissions|code contributions]].

@@ Line 33: / Line 33: @@
 === Developing a plugin ===
 First, you should consider which type of plugin you want to build. The [[PluginTypes|plugin types page]] provides a list of plugin types that can be implemented in Protege.
@@ Line 53: / Line 57: @@
 === Troubleshooting ===
 * [[SolvingClassLoaderProblems|Troubleshooting class loader issues]]
 === Contributing ===

← Older revision		Revision as of 05:56, May 24, 2016
Line 50:		Line 50:
	* [[Protege_5_Development_Environment\|Setting up a development environment for the OWL Ontology Server]]		* [[Protege_5_Development_Environment\|Setting up a development environment for the OWL Ontology Server]]
	* [[Protege_Server_design\|OWL Ontology Server design]]		* [[Protege_Server_design\|OWL Ontology Server design]]
		+
		+	=== Troubleshooting ===
		+	* [[SolvingClassLoaderProblems\|Troubleshooting class loader issues]]
		+
		+
		+	=== Contributing ===
		+
		+	'''Please share.'''
		+	It is surprising how many people have written plugins for Protege that we just don't hear about.<br />
		+	If you wish to publish to the community, please see our notes on [[Protege4Contributing#Code_submissions\|code contributions]].

← Older revision		Revision as of 05:51, May 24, 2016
Line 37:		Line 37:

	=== Developing a plugin ===		=== Developing a plugin ===
		+
		+	First, you should consider which type of plugin you want to build. The [[PluginTypes\|plugin types page]] provides a list of plugin types that can be implemented in Protege.
		+
		+	Second, take a look and reuse the [https://github.com/protegeproject/protege-plugin-examples/ plugin examples] available on GitHub. The GitHub page also has documentation (see the readme file). Clone the project, and then adapt the plugin example that you would like to implement.
		+
		+	You may also look at the [[PluginAnatomy\|Anatomy of a Plugin page]], which gives a quick start to writing a plugin for Protege. Although it was created for Protege 4 plugins, most things still apply to Protege 5 plugins. The page starts with a guide to writing the empty (trivial) plugin in five minutes. Then it describes how some additional content can be added to the plugin.
		+
		+	Once you have written a plugin you want people to use it. Some very simple steps allow you to advertise your plugin and [[EnablePluginAutoUpdate\|enable auto-update]].

@@ Line 29: / Line 29: @@
 ==== Protege Core APIs ====
-Here is a summary of the main parts of the [[P4APIOverview|Protege 4 API]] for gaining access to the model and various utilities.
+The [[P4APIOverview|Protege API]] gives access to the ontology model and offers various utilities.
 ==== UI components ====
-The Protege core and the OWL editor kit both provide a large number of [[P4UiComponentSummary|reuseable components]] and utilities for generating user interfaces for ontologies.
+The Protege core and the OWL editor kit both provide a large number of [[P4UiComponentSummary|reuseable UI components]] and utilities for generating user interfaces for ontologies.