Fiji renames its launcher to 'ImageJ'

[dscho]

Dear Fiji/ImageJ enthusiasts,

in the wake of the recent Fiji/ImageJ2 hackathon -- and also to try to fix
the confusion about Fiji having a different name from ImageJ -- the
next time your Fiji Updater runs it will rename the executable from
"fiji" to "ImageJ".

After all, Fiji Is Just ImageJ (but with a lot of convenience for the
users).

So what changes with the new name? Not much, except that you call Fiji
using the name "ImageJ-win64" or similar instead of "fiji-win64".

For true backwards-compatibility, the same launcher will be available
under the old name "fiji-...", too, although the next Fiji release will
only have the ImageJ-... binaries.

On MacOSX nothing will change even then: a double-click on the Fiji icon
will start it as usual. Likewise, the program to call after installing the
Debian packages is still called 'fiji'.

Rationale: Our plan is to have ImageJ2 and Fiji differ only in that the latter
bundles a few components targeted to life-science while ImageJ2 should be
the powerful core that is flexible enough for all kinds of image
processing/analysis purposes. To that end, many of Fiji's components will
be made part of ImageJ2 -- the Updater, the Script Editor, ImgLib2, etc.
And of course the launcher.

Stay tuned for more to come,
Johannes

[Jacqueline Ross]

Hi Johannes,

I run both classical ImageJ as well as Fiji since I have lots of Plugins that I have collected over the years in my original version.

Will I have any conflicts with the new "fiji"? I have to admit I haven't been keeping up with all of the correspondence regarding ImageJ2, etc.

Kind regards,

Jacqui

Jacqueline Ross

Biomedical Imaging Microscopist
Biomedical Imaging Research Unit
School of Medical Sciences
Faculty of Medical & Health Sciences
The University of Auckland
Private Bag 92019
Auckland, NEW ZEALAND

Tel: [phone] Ext 87438
Fax: [phone]

http://www.fmhs.auckland.ac.nz/sms/biru/

-----Original Message-----
From: ImageJ Interest Group [mailto:[hidden email]] On Behalf Of Johannes Schindelin
Sent: Thursday, 12 January 2012 8:11 a.m.
To: [hidden email]
Subject: Fiji renames its launcher to 'ImageJ'

Dear Fiji/ImageJ enthusiasts,

in the wake of the recent Fiji/ImageJ2 hackathon -- and also to try to fix
the confusion about Fiji having a different name from ImageJ -- the
next time your Fiji Updater runs it will rename the executable from
"fiji" to "ImageJ".

After all, Fiji Is Just ImageJ (but with a lot of convenience for the
users).

So what changes with the new name? Not much, except that you call Fiji
using the name "ImageJ-win64" or similar instead of "fiji-win64".

For true backwards-compatibility, the same launcher will be available
under the old name "fiji-...", too, although the next Fiji release will
only have the ImageJ-... binaries.

On MacOSX nothing will change even then: a double-click on the Fiji icon
will start it as usual. Likewise, the program to call after installing the
Debian packages is still called 'fiji'.

Rationale: Our plan is to have ImageJ2 and Fiji differ only in that the latter
bundles a few components targeted to life-science while ImageJ2 should be
the powerful core that is flexible enough for all kinds of image
processing/analysis purposes. To that end, many of Fiji's components will
be made part of ImageJ2 -- the Updater, the Script Editor, ImgLib2, etc.
And of course the launcher.

Stay tuned for more to come,
Johannes

[dscho]

Hi Jacqui,

On Wed, 11 Jan 2012, Jacqui Ross wrote:

> I run both classical ImageJ as well as Fiji since I have lots of Plugins
> that I have collected over the years in my original version.

Is this an up-to-date ImageJ? Then the same plugins should Just Work after
drag-n-dropping them onto Fiji.

> Will I have any conflicts with the new "fiji"? I have to admit I haven't
> been keeping up with all of the correspondence regarding ImageJ2, etc.

There should not be any conflict; the ImageJ launcher is installed into
Fiji.app and basically runs ImageJ (with a few convenience settings users
usually do not want to be bothered with).

But there is more, of course, the ImageJ launcher already knows how to
launch ImageJ2 (if the files are present)... ;-)

Ciao,
Johannes

[Jacqueline Ross]

Thanks Johannes,

That makes sense. Maybe I should consolidate...

Kind regards,

Jacqui

Jacqueline Ross

Biomedical Imaging Microscopist
Biomedical Imaging Research Unit
School of Medical Sciences
Faculty of Medical & Health Sciences
The University of Auckland
Private Bag 92019
Auckland, NEW ZEALAND

Tel: [phone] Ext 87438
Fax: [phone]

http://www.fmhs.auckland.ac.nz/sms/biru/


-----Original Message-----
From: Johannes Schindelin [mailto:[hidden email]]
Sent: Thursday, 12 January 2012 10:50 a.m.
To: Jacqui Ross
Cc: [hidden email]
Subject: Re: Fiji renames its launcher to 'ImageJ'

Hi Jacqui,

On Wed, 11 Jan 2012, Jacqui Ross wrote:

> I run both classical ImageJ as well as Fiji since I have lots of Plugins
> that I have collected over the years in my original version.

Is this an up-to-date ImageJ? Then the same plugins should Just Work after
drag-n-dropping them onto Fiji.

> Will I have any conflicts with the new "fiji"? I have to admit I haven't
> been keeping up with all of the correspondence regarding ImageJ2, etc.

There should not be any conflict; the ImageJ launcher is installed into
Fiji.app and basically runs ImageJ (with a few convenience settings users
usually do not want to be bothered with).

But there is more, of course, the ImageJ launcher already knows how to
launch ImageJ2 (if the files are present)... ;-)

Ciao,
Johannes