Hi Grant,<br><br>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.<br>
<br>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.<br>
<br>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.<br><br>Thanks,<br>Curtis<br><br><div class="gmail_quote">
On Tue, Aug 31, 2010 at 10:48 AM, Grant B. Harris <span dir="ltr"><<a href="mailto:gharris@mbl.edu">gharris@mbl.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Image Jayers --<br>
<br>
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.<br>
<br>
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.<br>
<br>
-- Grant<br>
<br>
_______________________________________________<br>
ImageJ-devel mailing list<br>
<a href="mailto:ImageJ-devel@imagejdev.org" target="_blank">ImageJ-devel@imagejdev.org</a><br>
<a href="http://imagejdev.org/mailman/listinfo/imagej-devel" target="_blank">http://imagejdev.org/mailman/listinfo/imagej-devel</a><br>
</blockquote></div><br>