Posted by
ctrueden on
Nov 11, 2012; 2:25am
URL: http://imagej.273.s1.nabble.com/Changing-fonts-in-macros-for-the-Series-Labeler-tp5000755p5000768.html
Hi Graeme & everyone,
Johannes Schindelin wrote:
> We will provide a very similar interface using Beanshell
> (
http://fiji.sc/Beanshell_Scripting) that will be able to call
> ImageJ2-specific functionality, but not all macros will run unchanged.
To elaborate, we have managed to create an almost-totally-compatible
Beanshell version of the ImageJ1 macro language. It still needs a bit more
work, but we believe that most ImageJ1 macros will run unchanged in
ImageJ2, while also allowing to mix and match any Java API calls—something
that was previously not possible with the macro language.
The ImageJ1 macro language has been extremely useful to many users.
However, it has a substantial limitation: its functions are separate from
those available from Java and the other scripting languages. In ImageJ2 the
goal is to provide one unified set of functions, which is fully accessible
from Java and all scripting languages. The Beanshell-based macro language
helps to meet that goal, and also makes the reverse possible: calling macro
functions from other scripting languages and from Java.
Graeme Ball wrote:
> do you consider it deprecated?
ImageJ2 plugins and scripts are more flexible than ImageJ1 plugins and
macros. They can run headless on a server, and are accessible from various
applications such as CellProfiler, KNIME, OMERO, and headless from the
command line. I would encourage newly developed scripts and plugins to use
the ImageJ2 API since it offers these advantages, but the ImageJ1 API will
remain accessible, too.
> do you see one of the existing scripting options becoming a new
> standard?
ImageJ2 will support a variety of scripting languages, like Fiji does now.
There is no one language intended to become a "standard" above the others.
Regards,
Curtis
On Fri, Nov 9, 2012 at 4:10 PM, Johannes Schindelin <
[hidden email]> wrote:
> Hi Graeme,
>
> On Fri, 9 Nov 2012, Graeme Ball wrote:
>
> > a question about ImageJ(2) scripting - going forward, it seems the
> > original ImageJ macro language will continue to be supported - but do
> > you consider it deprecated? and if so, do you see one of the existing
> > scripting options becoming a new standard? Javascript perhaps?
>
> The macro language will be limited to the legacy layer. We will provide a
> very similar interface using Beanshell (
http://fiji.sc/Beanshell_Scripting> )
> that will be able to call ImageJ2-specific functionality, but not all
> macros will run unchanged.
>
> Ciao,
> Johannes
>
> --
> ImageJ mailing list:
http://imagej.nih.gov/ij/list.html>
--
ImageJ mailing list:
http://imagej.nih.gov/ij/list.html