[ImageJ-devel] Headlessness

[Curtis Rueden]

Hi Grant,

I think the "abstract plugin" mechanism that Dscho & you developed is a good
start, at least for plugins. Then you do not need a global context flag, but
rather GenericDialog is only created in the GUI case. So plugins written
using that new style are one big step closer to working headless. I think it
is less important that older plugins work headless as-is—they can be
converted to use the new style, to solve the problem that way.

For Menus and Tools, I have not examined them in detail yet, so cannot
really comment. Do you have a list of the main offenders? Point to some line
numbers in code where it's a problem? It would help save me time.

Another thing we could do is write a program that is supposed to run
headless, run it so, and see where the exceptions are raised. Then solve
them one by one until it works.

Thanks,
Curtis

On Tue, Aug 31, 2010 at 10:48 AM, Grant B. Harris <gharris at mbl.edu> wrote:

>  Image Jayers --
>
> For running headless, ImageJA uses the trick of prepending the headless.jar
> to the classpath, replacing Menus, gui.GenericDialog, and util.Tools with
> modified GUI-less versions.
>
> If we are to enable running headless in a future version, I'd like to get
> ideas as to what strategies we might adopt (e.g. having a global flag in the
> application context which allows gui-less operation of plugins and other
> components,...)  Let's have a conversation on this.
>
> -- Grant
>
> _______________________________________________
> ImageJ-devel mailing list
> ImageJ-devel at imagejdev.org
> http://imagejdev.org/mailman/listinfo/imagej-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://imagej.net/pipermail/imagej-devel/attachments/20100831/2d2bd656/attachment.html>