Posted by
ctrueden on
Mar 04, 2011; 7:57pm
URL: http://imagej.273.s1.nabble.com/Fiji-Updater-for-deploying-ImageJ-was-Re-JarUpdater-An-easy-way-to-distribute-plugin-updates-tp3685016.html
Hi Jarek,
This is the multi-site updater feature of the upcoming Fiji release. There
> could even be minimal distributions which set up update sites already.
>
As Johannes says, your suggestion is exactly the direction we are taking
things. Fiji is the mechanism by which the ImageJDev team plans to deploy
ImageJ2 and accompanying plugins later this year.
While Fiji started out as a distribution mechanism for TrakEM2, Simple
Neurite Tracer and other otherwise-difficult-to-deploy plugins, it has
become clear that it can serve as a powerful and general deployment platform
for ImageJ across many different fields of endeavor. For example, we have
been working with the Micro-Manager team to better integrate Micro-Manager
and Fiji, using an update site maintained by the Micro-Manager team. The
core multi-updater functionality is largely functional now and as Johannes
indicated will be available with the forthcoming release of Fiji.
We recently had a Fiji/ImageJDev hackathon in Madison, where we made great
progress on these goals. (I will be sending an update email to the list next
week with a summary of our efforts.) We will keep the community posted as
these features develop.
Regards,
Curtis
On Fri, Mar 4, 2011 at 10:48 AM, Johannes Schindelin <
[hidden email]> wrote:
> Hi Jarek,
>
> On Fri, 4 Mar 2011, Jarek Sacha wrote:
>
> > Fiji is much more than the updater; it is also a distribution of large
> > amount of plugins. What would be nice, is to separate the updater
> > mechanism from the other Fiji plugins. Something similar to the Update
> > Centers provided, for instance, by Eclipse and NetBeans. User could
> > select which update centers to use. Even better which plugin clusters to
> > use. User could control which types of plugins he/she is interested in.
> > Having a standard way to provide plugins, other projects that provide
> > plugins (including the main ImageJ website) could setup their update
> > centers that would be registered with ImageJ website.
>
> This is the multi-site updater feature of the upcoming Fiji release. There
> could even be minimal distributions which set up update sites already.
>
> > I do appreciate the complexity of resolving dependencies and conflicts
> > between library versions, and creating update descriptions for the
> > updater. That is the reason why solution to this so appealing to many
> > users of ImageJ. Unless you are using Fiji with all of its plugins and
> > only its plugins, it has to be done manually.
>
> Unfortunately, I made myself misunderstood. For the updater to work, it is
> absolutely crucial that there is a custom launcher. We put a lot of work
> and thought into this (as well as some unfortunate trial and error), but
> if you think you can do better without Fiji (but still handling updating
> in-use files and dependencies properly), do go ahead.
>
> Hth,
> Johannes
>