ImageJ2 backwards compatibility, was Re: "cute" new syntax in macro language

[ctrueden]

Hi everyone,

Kees Straatman <[hidden email]> wrote:

> One thing that is not clear to me reading all the emails is if the macro
> language will disappear in ImageJ2 and will only be backwards-compatible for
> existing macros or will there still be a macro language in ImageJ2? And if
> so, will this be the same as in ImageJ1 or a different language?
>

To be perfectly clear: the first and foremost goal of the ImageJ2 project is
100% backwards compatibility with ImageJ1. This has been, and will continue
to be, our primary mission. No matter what, ImageJ2 will support existing
macros, plugins and scripts with no changes. This is possible because
ImageJ2 includes the latest version of ImageJ1 "under the hood" so that
existing code will still run the same as before.

A large part of our development effort has been the creation of a "legacy
layer" of IJ2 that is responsible for seamless integration of ImageJ1 within
the more powerful architecture of ImageJ2. This work has taken quite some
time, delaying the release of the beta, but we feel it is a key component of
IJ2 that must work well.

The ImageJ2 and Fiji projects are fully aligned in producing a painless
upgrade path from ImageJ1 to Fiji/ImageJ2. We share the community's concern
that existing workflows must continue to be supported. All involved
developers closely work together on that common goal.

In recent news, with the latest update, Fiji now uses stock ImageJ
(currently 1.45r, the most recent release version) and will continue to do
so. We are committed to collaborative development, and are working toward a
"Fiji2" release that uses ImageJ2 as its core.

Regarding the new expandable array syntax, we have tackled many similar
obstacles already, and are confident that we will find a solution
satisfactory to all.

Regards,
Curtis, Johannes, Kevin, Pavel and Albert, on behalf of the Fiji/ImageJ2
development team
http://imagejdev.org/
http://fiji.sc/


On Mon, Oct 17, 2011 at 3:35 AM, Straatman, Kees R. (Dr.) <
[hidden email]> wrote:

> Dear all,
>
> We have many users who have no background in programming and use the macro
> language because it is easy and does the job, so I really hope we don't lose
> this. When I was a postdoc I had the time to write some plugins but now I am
> too busy and I write all image analysis for ImageJ in the macro language and
> many more lines than 10. I don't know if this is good or bad but it is
> reality I am afraid. One thing that is not clear to me reading all the
> emails is if the macro language will disappear in Imagej2 and will only be
> backwards-compatible for existing macros or will there still be a macro
> language in ImageJ2? And if so, will this be the same as in ImageJ1 or a
> different language?
>
> Best wishes
>
> Kees
>
> Dr Ir K.R. Straatman
> Senior Experimental Officer
> Centre for Core Biotechnology Services
> College of Medicine, Biological Sciences and Psychology
>
> http://www.le.ac.uk/biochem/microscopy/home.html
>
>
> -----Original Message-----
> From: ImageJ Interest Group [mailto:[hidden email]] On Behalf Of
> Albert Cardona
> Sent: 16 October 2011 09:28
> To: [hidden email]
> Subject: Re: "cute" new syntax in macro language, was Re: Bug in newArray()
> macro function
>
> Dear Johannes,
>
> thanks for the detailed explanations. The problem is evident now. I
> support your decision to not be backwards-compatible with ImageJ-1
> regarding this one feature, extensible arrays. What surprises me is
> that other macro language features have not been a problem for
> rewriting the macro language using the BeanShell language. Cheers to
> you for accomplishing that feat.
>
> I have not used the macro language in years, perhaps five years. I
> find jython and clojure easier, more practical and, what matters, more
> useful. The ImageJ Macro Recorder is invaluable in figuring out how to
> run plugins on an image, as I elaborated on in the examples of the
> Fiji Jython Tutorial:
>
>
> http://www.ini.uzh.ch/~acardona/fiji-tutorial/#figuring-out-plugin-parameters
>
> http://www.ini.uzh.ch/~acardona/fiji-tutorial/#running-command-on-an-image
>
> As I have done before, I encourage ImageJ power-users reading this
> email to not rely on the macro language for programs longer than about
> 10 lines. There are better alternatives.
>
> Albert
>
> --
> http://albert.rierol.net
> http://www.ini.uzh.ch/~acardona/
>