Posted by
Albert Cardona-2 on
Jun 24, 2014; 3:46pm
URL: http://imagej.273.s1.nabble.com/FIJI-IJ2-script-editor-tp5008308p5008400.html
Hi Curtis,
while this reads great, removing the interpreters is not an option, given
their key position in enabling straightforward interactive image processing
a-la Matlab, but with all the java and ImageJ-specific libraries.
Additionally and as I commented in the bug tracker (
http://fiji.sc/bugzilla/show_bug.cgi?id=793 ), the interpreters have unique
capabilities, and many users rely on them for both the execution of complex
pipelines and the testing out and development of programs.
A note about the typed inputs and outputs in scripts: while I understand
why you'd want this feature, it cannot come at the cost of removing and not
replacing existing functionality.
Albert
2014-06-24 10:52 GMT-04:00 Curtis Rueden <
[hidden email]>:
> Hi Albert & everyone,
>
> > Why gut the working scripting framework to create a new one? It is
> > orthogonal to image processing and any data structures.
>
> The reasons we rewrote the scripting system are:
>
> 1) Integration with the ImageJ/SciJava module framework. This allows
> scripts to declare typed inputs and outputs, which are usable from other
> contexts besides just ImageJ.
>
> Example scripts at:
> *
>
>
https://github.com/imagej/imagej-tutorials/blob/577286474be8399eb38d30d66cf0c35ee50bd929/widget-demo/scripts/Widgets_BeanShell.bsh> *
>
>
https://github.com/imagej/imagej-tutorials/blob/577286474be8399eb38d30d66cf0c35ee50bd929/widget-demo/scripts/Widgets_JavaScript.js>
> Example commands in Java:
> *
>
>
https://github.com/imagej/imagej-tutorials/tree/577286474be8399eb38d30d66cf0c35ee50bd929/simple-commands/src/main/java>
> Tutorial explaining modules:
> *
>
>
https://github.com/imagej/imagej-tutorials/blob/577286474be8399eb38d30d66cf0c35ee50bd929/working-with-modules/src/main/java/WorkingWithModules.java>
> Such modules are UI agnostic, and already usable from CellProfiler, KNIME,
> OMERO and Alida [1].
>
> 2) Extensibility. It is now feasible to add additional scripting languages
> to ImageJ, because scripting languages are just plugins. Johannes has
> already done Scala [2] and we are also half done with R [3]. No code
> changes to the core codebase are required. So anyone can add a new ImageJ
> update site that adds support for new scripting languages.
>
> Regards,
> Curtis
>
> [1] See also:
http://developer.imagej.net/2014/04/04/announcing-imagej-ops> [2]
https://github.com/scijava/scripting-scala> [3]
https://github.com/scijava/scripting-r>
>
> On Thu, Jun 19, 2014 at 6:49 PM, Albert Cardona <
[hidden email]>
> wrote:
>
> > > On Jun 19, 2014, at 6:47 PM, Johannes Schindelin <
> >
[hidden email]> wrote:
> > >
> > > Hi Albert,
> > >
> > >> On Thu, 19 Jun 2014, Albert Cardona wrote:
> > >>
> > >> As the creator of the interpreters, I would prefer if they were to
> > >> remain.
> > >
> > > But... how dedicated are you in that goal? Will you port them to the
> > > SciJava scripting framework, as I had indicated I would not be able
> > afford
> > > the time?
> > >
> > > Ciao,
> > > Johannes
> >
> >
> > Johannes,
> >
> > Once you told me "never ever change a working system".
> >
> > Why gut the working scripting framework to create a new one? It is
> > orthogonal to image processing and any data structures.
> >
> > Alert
> > --
> > ImageJ mailing list:
http://imagej.nih.gov/ij/list.html> >
>
> --
> ImageJ mailing list:
http://imagej.nih.gov/ij/list.html>
--
http://albert.rierol.nethttp://www.ini.uzh.ch/~acardona/--
ImageJ mailing list:
http://imagej.nih.gov/ij/list.html