Jan Eglinger

Having a *Load from file...* option for image inputs would avoid situations of poor user experience such as the one mentioned [in this forum thread](https://forum.image.sc/t/noise2void-for-fiji/34552/33?u=imagejan). /cc @frauzufall

When calling from macro or via the command line, SCIFIO's [`StringToDatasetConverter`](https://github.com/scifio/scifio/blob/741ac2ac03ec4c566a6612c0f148fdd47bd47d9d/src/main/java/io/scif/convert/StringToDatasetConverter.java) takes care of converting `String` inputs to images by loading from file. What's still required is a way to...

Interesting. In what circumstances is `CommandService.run()` called from the EDT? I've never seen this in my commands, and just wondered why the issue doesn't occur more often then. If you...

If you don't need to programmatically access the outputs, but just trigger running the command, you won't need `get()`, right.

I refactored `ScriptServiceTest` a bit to initialize the `Context` in a `@Before` method, and dispose it `@After` the tests. @ctrueden what do you think about the re-use of the `ScriptLanguage`...

@NicoKiaru absolutely, it could solve the problem of having `Pet@57a3e26a` instead of `Felix` as a name in your example. In general, this allows giving names to any object of a...

@NicoKiaru iff the change proposed here gets merged and included in a release, and then the change from `v.toString()` to `objectService.getName(v)` you proposed in https://github.com/imagej/imagej-legacy/pull/243/files#diff-de04251535e202b6132a0485276551de8ec4b1e86a639a9b54c67d63527ef5e1R251 is indeed sufficient to have...

Ah, we do have [`AbstractSciJavaTest`](https://github.com/scijava/scijava-common/blob/afe795ae2179dec8b2a33ad1048b5ffd85651f8b/src/test/java/org/scijava/test/AbstractSciJavaTest.java) already, but it doesn't appear to be used anywhere in the codebase I searched.

See [this forum topic](http://forum.imagej.net/t/brightness-and-contrast-for-composite-images/11151/2?u=imagejan) for some use case where a range input would be useful.

I'm not sure about the current status of the parameter visibility implementation. When testing with scripts, only the `MESSAGE` option seems to have an effect: ```groovy #@String(visibility=NORMAL, value="T1") t1 #@String(visibility=TRANSIENT,...