Difference between revisions of "Protege4DevDocs"
(→Compiling and Running the Protege-OWL editor) |
(→Compiling and Running the Protege-OWL editor) |
||
| Line 25: | Line 25: | ||
=== Compiling and Running the Protege-OWL editor === | === Compiling and Running the Protege-OWL editor === | ||
| − | The following two | + | The following two links cover much the same ground. They describe how to download, compile and run the protege 4 sources in a development environment. |
* [http://www.cs.man.ac.uk/~iannonel/eclipseSetup/eclipseSetupMain.html Compile and run the Protege 4 OWL Editor in Eclipse] <b>(External link)</b> - this page gives directions for compiling Protege 4.0 sources in Eclipse where ''all bundles are encapsulated in one Eclipse project'' | * [http://www.cs.man.ac.uk/~iannonel/eclipseSetup/eclipseSetupMain.html Compile and run the Protege 4 OWL Editor in Eclipse] <b>(External link)</b> - this page gives directions for compiling Protege 4.0 sources in Eclipse where ''all bundles are encapsulated in one Eclipse project'' | ||
Revision as of 21:01, April 7, 2008
Protege 4 Developer Documentation
This page is still somewhat under construction...
Contents
Working with the Protege source code
Preliminaries
TODO: We need a high-level description here about how the 4.x source code is organized, since it's different than the 3.x series, e.g. we are using the OSGi plug-in architecture now, etc.
Before loading the Protege 4 sources into Eclipse, developers need to decide if they want all of the Protege sources in one big project or if they want separate projects for each of the Protege 4 plug-ins. We put together a list of pros and cons of working with one big project vs. several smaller projects. You may want to read the condensed version first (below), which often leads to an answer:
- Eclipse developers will generally favor having several smaller projects. Eclipse provides nice support for defining extensions and extension points and will detect problems in both manifest files and the plugin.xml files.
- Plug-in developers will generally do better with several smaller projects since they do not need to make changes to the core Protege sources. They can also choose an appropriate Protege 4 build to create runnables.
- Non-Eclipse developers who are working with all the Protege sources (e.g., the Protege development team or developers who need tight coordination with Protege sources) will probably prefer to work with one single large project.
Once this decision has been made, please refer to the next section on compiling and running Protege 4. Instructions for both methods of working with the source code are outlined in detail.
Compiling and Running the Protege-OWL editor
The following two links cover much the same ground. They describe how to download, compile and run the protege 4 sources in a development environment.
- Compile and run the Protege 4 OWL Editor in Eclipse (External link) - this page gives directions for compiling Protege 4.0 sources in Eclipse where all bundles are encapsulated in one Eclipse project
- Compile and run the Protege-OWL editor in Eclipse In Progress - this page gives directions for compiling Protege 4.0 sources in Eclipse where all bundles are encapsulated in one Eclipse project.
The next link covers the problem of compiling and running a plugin in a development environment.
- Setting up the IDE environment for a plugin in Eclipse (In Progress) -this page gives directions for setting up eclipse to do development work on a plugin.
The following link will be updated later when we have better details on how to run Protege 4 using the eclipse OSGi debugging capabilities.
- Compile and run the Protege 4 OWL editor in Eclipse (In Progress)- this page gives directions for compiling Protege 4.0 sources in Eclipse where each bundle is created as a separate Eclipse project.
Writing a simple view plugin (with example code)
A short guide to writing a plug-in to show the class hierarchy. This doesn't delve deeply into setting up your build environment, but concentrates on a simple code example and making sure you understand the components and the structure of a plug-in.
