Mark Hiner

@MarijaMatejcic definitely! [Here](https://imagej.github.io/events/wiki-grand-opening/page-list) is the page list. [Here](https://imagej.github.io/events/wiki-grand-opening/how-to-help#choosing-a-page-to-work-on) is a suggestion on how to pick pages.

from @ctrueden >@hinerm Talking more with @elevans, we think that the synchronize_ij1_to_ij2 call (which I'd support renaming to just sync or similar) needs to go at the end of run_script...

see also #74

@elevans verify that #74 is fixed when completing this issue

Notes from talk with @ctrueden: * The script argline can be generated at the same time as the parameters * For boolean parameters use a ternary operator since the string...

thanks for looking into this @kephale. Does the [deployed 6.0.2 linux64 exe](https://maven.scijava.org/service/local/artifact/maven/redirect?r=releases&g=net.imagej&a=imagej-launcher&v=6.0.2&e=exe&c=linux64) correctly make the XInitThreads call? https://github.com/imagej/imagej-launcher/commit/0c3902642829b40a8ed72edd5ea3fbc1a3872acf is the only commit after `6.0.2` and it seems like that would...

>Do you feel the current launcher code has ironed out all the problems raised by the community @ctrueden no I think if we didn't upload a 6.x before there was...

[JavaFX](http://docs.oracle.com/javase/8/docs/technotes/guides/deploy/self-contained-packaging.html#BCGIGHHC) may solve this issue

However, we need to document what features we may be losing from migrating to JavaFX..

Note that whatever solution we settle on we also should ensure our Java3D problems are solved forever and ever. @ctrueden has a fork of Java 3D 1.6 that is Mavenized.....