newImage() does not work in "modern mode".

[Gelman, Laurent]

Hi everybody,

I was testing some of my home-made macros in the new imageJ "Modern mode", and I encountered many problems.

For example:
SetBatchMode(...) does not seem to work properly.
Also, no new image appears if I type newImage("Tile", "8-bit black", 512,512,1);

Is this normal? Will I have to keep an old version of Fiji/ImageJ in the future to run my old macros? Will a "Legacy mode" be always available in the future?

Thanks and best regards,

Laurent.


_____________________________________________
Laurent Gelman, PhD
Head of Facility for Advanced Imaging and Microscopy
(Light Microscopy)

Friedrich Miescher Institut
WRO 1066.2.16
Maulbeerstrasse 66
CH-4058 Basel
[phone]
[phone]


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

[dscho]

Hi Laurent,

On Thu, 15 Aug 2013, Gelman, Laurent wrote:

> I was testing some of my home-made macros in the new imageJ "Modern
> mode", and I encountered many problems.

Please keep in mind that as per my mail here:

        http://article.gmane.org/gmane.comp.java.imagej.devel/1696

the "Switch to Modern Mode" feature is *highly* experimental at the
moment. For now, I am glad that we did not have *too* many regressions in
the legacy mode, and I will concentrate on the latter in the next few
weeks (except next week and the week thereafter).

> For example:
> SetBatchMode(...) does not seem to work properly.
> Also, no new image appears if I type newImage("Tile", "8-bit black", 512,512,1);
>
> Is this normal?

No, but expected. The modern mode is so far only intended for early
adoption by developers, not by users. It will take some effort to
stabilize the legacy part in the modern mode.

> Will I have to keep an old version of Fiji/ImageJ in the future to run
> my old macros?

Hopefully not. For now, use the legacy mode to run macros, though, the
modern mode is not at all prepared for macros (if you have been around
during the discussions about forward-compatibility of the macro language,
you'll know why).

> Will a "Legacy mode" be always available in the future?

Since it is our conviction that backwards-compatibility should be
maintained as much as humanly possible (and sometimes, even more, e.g. by
patching methods back into the legacy mode that have gone away from ij.jar
without prior warning): yes.

We will always work hard to maintain support for a legacy mode, even if it
implies ugly work-arounds. The idea of Fiji/ImageJ2 is really to support
users better, while maintaining as elegant code as possible under that
limitation.

Ciao,
Johannes

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