Difference between revisions of "Protege5DevDocs"

From Protege Wiki
Jump to: navigation, search
Line 29: Line 29:
 
==== Protege Core APIs ====
 
==== 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.  
 
 
The code for Protege core is available in [https://github.com/protegeproject/protege GitHub].
 
  
 
==== UI components ====
 
==== 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.
  
  

Revision as of 22:39, May 23, 2016

Protege Desktop 5.x Developer Documentation

This page is a top-level entry point for all developer documentation related to the Protege Desktop application, versions 5.0 and above.


Building

Accessing the source code

Protege Desktop is open source and the code is freely available on GitHub. Use the following Git command to get a local copy:

git clone https://github.com/protegeproject/protege.git protege

The source code for many Protege Desktop plug-ins has also been made available on GitHub under the Protege Project organization.

Building from source

The instructions for building from source are available on GitHub.

Building with Eclipse and other IDEs

We would welcome contributions from the community for setting up development environments other than Eclipse.


Protege APIs

Protege Core APIs

The 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 reuseable UI components and utilities for generating user interfaces for ontologies.


Developing a plugin

Client-server