Protégé plugin development - practical project issues

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Protégé plugin development - practical project issues

Karl Hammar
Hello all,

I will over the course of the next few months be developing a plugin for Protégé, porting over and extending upon some functionality that existed as plugins for the NeOn Toolkit. I have a rough prototype version of this plugin, developed by a student, running on Protégé 4.1, which I will use as a starting point for further work.

Before getting further into the development work, I've got some questions that I'm hoping this list may be able to assist with;

1) What is the recommended way of setting up a development environment for a Protégé plugin project? I'm looking at using Eclipse. http://protegewiki.stanford.edu/wiki/Protege4DevDocs indicates that Maven may be used/supported moving forward, but that the Maven stuff was, at the time that page was authored, not quite ready for prime-time. Is this still the case?

2) http://protegewiki.stanford.edu/wiki/Main_Page indicates that Protégé 5.0 development is underway. Are there any estimates on when this version will be released? I'm considering whether to put effort into tracking the development branch when developing my plugin, or whether to develop targeting the 4.3 version instead.

3) Are there any changes between Protégé 4.1 and the more recent versions (either 4.3 or the latest 5.0 development tree) that are particularly likely to cause breakage of plugins, that I might need to be aware of?

Many thanks for any input you may have. And many thanks on your excellent work with Protégé, of course!

Best regards,

Karl Hammar

_______________________________________________
protege-dev mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-dev
Reply | Threaded
Open this post in threaded view
|

Re: Protégé plugin development - practical project issues

Jennifer Vendetti
Administrator
Hi Karl,

On 5/9/2014 2:22 PM, Karl Hammar wrote:

> I will over the course of the next few months be developing a plugin
> for Protégé, porting over and extending upon some functionality that
> existed as plugins for the NeOn Toolkit. I have a rough prototype
> version of this plugin, developed by a student, running on Protégé
> 4.1, which I will use as a starting point for further work.
>
> Before getting further into the development work, I've got some
> questions that I'm hoping this list may be able to assist with;
>
> 1) What is the recommended way of setting up a development environment
> for a Protégé plugin project? I'm looking at using Eclipse.
> http://protegewiki.stanford.edu/wiki/Protege4DevDocs indicates that
> Maven may be used/supported moving forward, but that the Maven stuff
> was, at the time that page was authored, not quite ready for
> prime-time. Is this still the case?

Have a look at the following recent post from our archive regarding the
state of our developer documentation and links that you might find
helpful for Eclipse:

http://protege-project.136.n4.nabble.com/My-Hello-Protege-plugin-Failure-to-build-source-code-tp4660326p4660334.html

The only news since the above post is that we created a repository in
GitHub with example code for developing tab, view, and menu plug-ins:

https://github.com/protegeproject/protege-plugin-examples

This doesn't help you with Eclipse, but the POM file in the root
directory is a useful reference if you want to use Maven for packaging
your plug-in as an OSGi bundle.

> 2) http://protegewiki.stanford.edu/wiki/Main_Page indicates that
> Protégé 5.0 development is underway. Are there any estimates on when
> this version will be released? I'm considering whether to put effort
> into tracking the development branch when developing my plugin, or
> whether to develop targeting the 4.3 version instead.

We're hoping to have an initial 5.0 beta build out by the end of this month.

> 3) Are there any changes between Protégé 4.1 and the more recent
> versions (either 4.3 or the latest 5.0 development tree) that are
> particularly likely to cause breakage of plugins, that I might need to
> be aware of?

I can't think of anything offhand.  Feel free to post again if you run
into issues.

Best,
Jennifer

_______________________________________________
protege-dev mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-dev