Difference between revisions of "Protege4DevDocs"
(→Writing a simple view plugin (with example code)) |
(→Compiling and Running the Protege-OWL editor) |
||
| Line 20: | Line 20: | ||
* [[CompileProtege4PluginInEclipseOneProject|Setting up the IDE environment for a plugin in Eclipse]] <b>(In Progress)</b> -this page gives directions for setting up eclipse to do development work on a plugin. | * [[CompileProtege4PluginInEclipseOneProject|Setting up the IDE environment for a plugin in Eclipse]] <b>(In Progress)</b> -this page gives directions for setting up eclipse to do development work on a plugin. | ||
| + | |||
| + | === Eclipse Only Instructions === | ||
| + | |||
| + | Unlike the approaches for plugin development described above, the following instructions are only relevant to eclipse developers. The eclipse environment has special support for OSGi and is - as far as I know - the best IDE environment for developing OSGI applications. Unfortunately there are some issues with taking advantage of this support that have not yet been worked out (involving Swing vs. SWT) so this documentation is still not complete. | ||
The following link is not complete yet and will be updated later when we have better details on how to run Protege 4 using the eclipse OSGi debugging capabilities. Hopefully we will complete this page because this method of loading Protege 4 plugins into eclipse will have some major advantages. | The following link is not complete yet and will be updated later when we have better details on how to run Protege 4 using the eclipse OSGi debugging capabilities. Hopefully we will complete this page because this method of loading Protege 4 plugins into eclipse will have some major advantages. | ||
Revision as of 11:45, April 11, 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
Right now we only have documents for how to work with eclipse. But I believe that developers using other IDE's will be able to follow these instructions (making the necessary changes as they go).
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.
Eclipse Only Instructions
Unlike the approaches for plugin development described above, the following instructions are only relevant to eclipse developers. The eclipse environment has special support for OSGi and is - as far as I know - the best IDE environment for developing OSGI applications. Unfortunately there are some issues with taking advantage of this support that have not yet been worked out (involving Swing vs. SWT) so this documentation is still not complete.
The following link is not complete yet and will be updated later when we have better details on how to run Protege 4 using the eclipse OSGi debugging capabilities. Hopefully we will complete this page because this method of loading Protege 4 plugins into eclipse will have some major advantages.
- 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.
