Login  Register

Re: Java, Linking and Portability

Posted by Benjamin Eltzner on Sep 12, 2014; 10:24am
URL: http://imagej.273.s1.nabble.com/Java-Linking-and-Portability-tp5009568p5009600.html

Hi Johannes,

thank you for re-adding this conversation to the list. My private answer
was just a mistake. Thank you for your further explanation of the Maven
workflow.

> Instead, the workflow is something like this:
>
> 1) Develop your plugin in an IDE such as Netbeans
>
> 2) When satisfied that it works as intended, i.e. when all the
>   unit tests pass, you install your plugin into an existing,
>   up-to-date Fiji (downloaded and unpacked from http://fiji.sc/):
>
> mvn -Dimagej.app.directory=/path/to/Fiji.app
>
>   This will automatically install also the dependencies that are
>   not present in that Fiji installation yet.
>
> 3) *Test the plugin in Fiji*
>
> 4) Start the updater with Help>Update... and upload to your update
>   site (initializing your own personal update site if you have
>   not done so yet).
>
>   The updater will suggest to upload dependencies that are not
>   available in Fiji yet, too.
>
> Of course you can also distribute your own ImageJ with your plugin, in a
> more manual process, but then you should not ask the person who worked so
> hard to make the process more automated ;-)

However, I think there is a missing bit of information here, namely
this: My program does not only do image processing but also data
processing and most importantly includes a basic GUI and data management
code that is geared towards its use case. I think it would not be
feasible to convert all this into ImageJ plugins (at least not in ImageJ
1). If I am mistaken here, I would be glad for any pointers to a
tutorial on how to build an alternate GUI as a plugin (set).

So with my current understanding of the scope of ImageJ and its plugin
system, I would like to use ImageJ only as a backend for image
processing (but in the course of this I would transform some of my
current image processing code into ImageJ plugins) and otherwise treat
my program as a standalone project. (Even if it is feasible to also do
the GUI and data analysis tools in terms of ImageJ plugins, I would like
to go through such an intermediary phase, as the program already has
more than 10.000 lines of code and a transition will take time which I
currently do not have abundantly.)


Best Regards,

Benjamin

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html