Difference between revisions of "Protege4DevDocs"
(→Compiling and Running the Protege-OWL editor in a Generic IDE) |
(→Compiling and Running a Plugin for Eclipse Users Only (Windows and Linux only)) |
||
| Line 22: | Line 22: | ||
=== Compiling and Running a Plugin for Eclipse Users Only (Windows and Linux only) === | === Compiling and Running a Plugin for Eclipse Users Only (Windows and Linux only) === | ||
| − | Unlike the approaches for plugin development described above, the following instructions are only relevant to eclipse developers. | + | Unlike the approaches for plugin development described above, the following instructions are only relevant to eclipse developers. These instructions use the OSGi development capabilities of eclipse (aka plugin development or rich client platform development). |
| + | As far as I know - eclipse is the best IDE environment for developing OSGI applications. | ||
| + | |||
| + | Unfortunately - though we now know that this works - we have not yet finished the documentation. While this also has not yet been verified, it may be necessary to download the latest version of eclipse to get the OSGi runnable to work. | ||
* [[CompileProtege4InEclipse|Compile and run the Protege 4 OWL editor in Eclipse]] <b>(In Progress)</b>- this page gives directions for compiling Protege 4.0 sources in Eclipse where ''each bundle is created as a separate Eclipse project''. | * [[CompileProtege4InEclipse|Compile and run the Protege 4 OWL editor in Eclipse]] <b>(In Progress)</b>- this page gives directions for compiling Protege 4.0 sources in Eclipse where ''each bundle is created as a separate Eclipse project''. | ||
Revision as of 07:05, April 17, 2008
Protege 4 Developer Documentation
This page is still somewhat under construction...
Contents
Working with the Protege source code
Compiling and Running the Protege-OWL editor in a Generic IDE
This section describes how to set up an IDE for plugin development. We describe this in two steps - first the core Protege sources are downloaded and compiled and then a plugin project is created. While these instructions were put together using eclipse we believe that they can be applied to other development environments and we welcome contributions from people using other development environments.
- Downloading, compiling and running the core Protege sources. The following two links cover much the same ground.
- 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 - this page gives directions for compiling Protege 4.0 sources in Eclipse where all bundles are encapsulated in one Eclipse project.
- Compiling and running a plugin.
- 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.
Compiling and Running a Plugin for Eclipse Users Only (Windows and Linux only)
Unlike the approaches for plugin development described above, the following instructions are only relevant to eclipse developers. These instructions use the OSGi development capabilities of eclipse (aka plugin development or rich client platform development). As far as I know - eclipse is the best IDE environment for developing OSGI applications.
Unfortunately - though we now know that this works - we have not yet finished the documentation. While this also has not yet been verified, it may be necessary to download the latest version of eclipse to get the OSGi runnable to work.
- 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.
