Skip to content

Instantly share code, notes, and snippets.

@dscho dscho/gist:2998994

Created Jun 26, 2012
Embed
What would you like to do?
The Road to Fiji2
Always addressing a concrete need, Fiji started out as a very small
distribution of ImageJ with a modern Java Virtual Machine and a curated
selection of plugins which were used a lot in life sciences. One of the key
advantages was that Fiji came with an Updater that made deploying new versions
of ones' plugins very easy, both for users but in particular for developers.
This attracted a growing number of users and developers to the project, and
consequently a growing number of tools were added that catered not directly to
life sciences but more to working with ImageJ and Fiji. Additions included: the
script editor, a build system that compiles all of Fiji's source code from
scratch, a plugin to ease making helpful bug reports, and a powerful updater to
for keeping Fiji up to date. Likewise, ImgLib was developed in the context of
Fiji, becoming so powerful that it now forms the basis of ImageJ2 and other
projects. With the modular design of ImageJ2, we can put the Fiji components
which are unrelated to life sciences back into ImageJ without bloating it, and
without losing backwards compatibility benefit from ImageJ2's powerful
architecture. Since the Fiji and the ImageJ developers have always worked
together closely, user-visible changes will be minor, but the Fiji project will
be able to focus on life sciences again in the future.
Keywords: imagej2, imglib, fiji, life science
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.