Difference between revisions of "Protege4DevDocs"

Revision as of 03:09, March 9, 2009

Guidelines

If you are writing code for P4, please compile it with java 1.5 for compatibility.
All current Protege 4.0 code is written in java 1.5. This will continue to be the case until Apple supports Java 6.

Please consider writing any P4 code as a plugin.
If you cannot do this for various reasons, please let us know as we may be able to improve the core design in order to support you.
Protege 4.0 has been written specifically to be modular. It uses equinox, one implementation of an OSGi framework to allow plugins to be created easily.

Please share.
It is surprising how many people have written plugins for P4 that we just don't hear about.
If you wish to publish to the community, please see our notes on code contributions.

Working with the Protege source code

Compiling and Running

Protege-OWL editor in IntelliJ

• Compile and run the Protege 4 Editor in IntelliJ

Protege-OWL editor in Eclipse (In Progress)

• Compile and run the Protege 4 Editor in Eclipse

Protege-OWL editor in a Generic IDE

This section describes how to set up an IDE for plugin development. While we have used eclipse to illustrate these pages, we have tried to describe an approach that is generic and will work for all IDE platforms. We welcome others to add pages above to describe how to get Protege 4 running in their favorite IDE. We describe this in two steps - first the core Protege sources are downloaded and compiled and then a plugin project is created.

• 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 a generic IDE (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 a Generic IDE - 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 a Generic IDE - this page gives directions for setting up eclipse to do development work on a plugin.

Anatomy of a Plugin

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.

This page also contains some information about the different parts of a plugin and how they work together. It also includes a very simple plugin and shows how to install it into the eclipse development environment.

The example delves into producing a view plugin, but we also have a short list of other useful plugin types that you may wish to implement (such as menu items etc).

Once you have written a plugin you want people to use it. Some very simple steps allow you to advertise your plugin and enable auto-update.

Key Classes

Please check out the javadoc for Protege 4.0 code.

The most important three classes you will have access to from most plugins are:

• OWLModelManager Access to the ontologies, reasoners, search renderings, change management etc
• OWLWorkspace Access to the UI elements (menus, cell renderers, handy entity selectors), global selection management etc
• OWLEditorKit The central access point for all of the model and UI elements of the OWL editor - you can get to both of the above from the editor kit

UI classes

There are many standard UI components, including all of the abstract view classes in org.protege.editor.owl.ui.view, and Protege 4.0 style lists in org.protege.editor.owl.ui.frame.

There are also many reusable UI components available such as OWLObjectTree, ExpressionEditor and standard dialogs in UIHelper.

Troubleshooting

• Troubleshooting class loader issues

Building The FaCT++ jni library

Because FaCT++ is written in C++, it is a little harder to get it to compile properly across platforms. In particular, a user may see errors such as

Link (dyld) error:
Symbol not found: _clock$UNIX2003

or a java.lang.UnsatisfiedLinkError with a message similar to the following

libFaCTPlusPlusJNI.so: /usr/lib/libstdc++.so.6: version `GL IBCXX_3.4.9' not found (required by libFaCTPlusPlusJNI.so)

This happens because the version of FaCT++ that was compiled into the Protege 4 owl editor is not compatible with the libraries in the users operating system. If this happens on a windows or an OS X machine then send a message to the P4 mailing list because the developers probably should fix this situation. (If you are not subscribed to this list look at this web page.) However on a linux or other operating system this is much more difficult because there are too many different variants. In this case you will probably have to build you own version of FaCT++. Hence we added the following page to make the work a little easier.

• Building the FaCT++ JNI Library