Jan Eglinger

This came up again in a [discussion on the forum](http://forum.imagej.net/t/parameter-issue-imageplus-versus-dataset-versus-img/6197/6?u=imagejan) related to https://github.com/imagej/imagej-legacy/issues/166. As it is in fact an issue in either `imagej/imagej` or `imagej/imagej-legacy`, we should probably close here...

For the record: JLine is now at [version 3](https://github.com/jline/jline3)

In a `DynamicCommand`, you can use a `callback` annotation to call methods that change values of inputs (and messages in case of `visibility=MESSAGE`). For scripts, this is more difficult since...

What is the current state of this? Can it be closed, since #259 is merged?

I guess a first step would be to fix the result of `supports` for those cases where lossless conversion currently is _not_ possible/implemented. ```groovy #@ ConvertService cs #@OUTPUT boolean stringToFile...

Yes, `#@----` is a good idea. When I first discovered this issue, I was concerned that the current behavior is against the principle of least astonishment: I'd assume that the...

Just an update: the `menuPath` issue is still not solved, scripts don't show up at the defined menu path, but at the one corresponding to their subfolder of `./scripts/`. Also,...

@ctrueden wrote: > Is there any reason not to simply cherry-pick ad139e7 right now? There's no reason not to do that :slightly_smiling_face: I rebased onto master and opened PR https://github.com/scijava/scijava-common/pull/331...

Yes, we still need to sort out the menu path.

After discussing with @ctrueden, we agreed on this syntax: ```groovy #@ int integer #@ String string #@callback("integer") string = "" + integer #@end #@callback("string") integer = Integer.parseInt(string) #@end ```