SWI-Prolog JPL up running inside Bioclipse - Thinking about next steps

So, today I finally got the jpl (Java / Prolog API) up running inside Bioclipse, succeeding with compiling a simple test prolog program (The "test 0" in the "Test" example supplied with SWI-Prolog). Only talking to swi-prolog so far though, not blipkit. Starting blipkit includes loading prolog files etc. as specified in the blipkit startup script, so will have to study that in more detail.

"Refcards" for quickly getting into Bioclipse Plug-in development

A link by Arvid led me to Dzone, where I found their "refcards": and after 15 minutes of reading, a lot of things, like file structure of Eclipse plug-in projects, had became much clearer.

For anyone new to Bioclipse plugin development, I think the following ones are the most relevant (especially the first two):

  • Eclipse Plug-in Development
  • Getting started with Equinox and OSGi
  • Spring Configuration
  • Spring Annotations

You will have to register at the site, and browse through the available ones in order to find them

Eclipse boot process, classloading, incorporation of native code etc.

This was a very good article on classloading and booting etc. in Bioclipse, with indispensable hints for how to best incorporate native code in eclipse plugins.


Prolog plugin for Eclipse

As a side-note, this looks interesting (Googled up by Egon), a Prolog Eclipse Plugin:

Could be interesting to combine that, in the future, with the results of my current project. Worth thinking about at least.

[SOLVED] How to set java.library.path for an Eclipse/Bioclipse plugin?

EDIT: Se solution at the bottom of the page

I'm trying to set the java.library.path system setting for my Bioclipse manager/Eclipse plugin.

Normally, if running java from command line, this variable should be set like so (According to what I've googled up):

java -Djava.library.path=/usr/local/lib/pl-5.7.15/lib/i686-linux/JavaClassName

so I have tried to add the line


to the arguments in "Run" > "Run configurations" for my plugin's product file, under the "arguments" tab.

Proposed plan of attack for BioclipseWiki

Being completely new to development for Bioclipse, I'm trying to dig into the developer-centric information available, primarily on the Bioclipse Wiki. Thinking that the feedback from a newcomer might be of some value, I'll below share my reflections and ideas for the wiki.

MediaWiki as platform

I think it has been a wise choice to use MediaWiki as a backend. since it is today becoming a de facto standard, both for huge community-driven knowledge bases with millions of users, as well as in the industry.

Plugin development for Bioclipse - from scratch

I switched laptop recently, so I needed to set up my development environment for Bioclipse 2.2 plugin development from scratch. Since the instructions for how to do this are spread over a couple of blogs and the wiki, I used the occasion to create an integrated howto, for my own documentation as well as for anyone interested.

[SOLVED] "Could not find library -lXpm" when building The SWI-Prolog XPCE package

When trying to build swi-prolog packages from source, the xpce package complains:

Keeping track of installed files when building from source, in Ubuntu

I ran into the trouble that I needed to clean up some software built from source, that did not have the "make uninstall" option, what a mess!

Just found a solution though: paco. Paco keeps track of installed files if you run "make install" through it. Later you can easily remove the installed packages.


On the two main approaches for knowledge handling on the Semantic Web

Egon pointed me to an interesting blog post on RIF and OWL. The post highlights a situation very relevant for my project: The apparent existence of two main approaches in the field of "knowledge representation and reasoning" (maybe it should be called simply handling?) on the Semantic Web.