A link by Arvid led me to Dzone, where I found their "refcards": http://refcardz.dzone.com/ 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):
You will have to register at the site, and browse through the available ones in order to find them
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.
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.
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):
so I have tried to add the line
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.
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.
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.
When trying to build swi-prolog packages from source, the xpce package complains:
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.
JPL is a bi-directional Java/Prolog interface for SWI-Prolog, which I hope to be able to use for integrating Blipkit into Bioclipse, so I'm happy to have got it up running tonight. Below are some notes from the installation procedure.
NOTE: These are still rather incomplete notes about how to get this to work.