Hidden but macro callable Commands

[Christian_Tischer]

@imagejan @haesleinhuepf

Do you know whether it is possible to have Commands that can be called from an IJ Macro, but that do not show up in the Fiji Menu tree?

Use case: I have my own GUI and just need the Commands such that whatever people do in my GUI can be recorded as a script.

[haesleinhuepf (Robert Haase)]

Hi @Christian_Tischer,

with the Command from Macro plugin by @uschmidt83 (comes via StarDist update site) you can, as discussed here:

Noise2Void for Fiji

Hey @DaleM, I’m just guessing the parameters from the example @frauzufall mentioned. I assume it’s something like modelFile = "path/to/model.file"; run("Command From Macro", "command=[de.csbdresden.n2v.command.N2VPredictCommand], args=['input, '" + getTitle() + "','modelFile', '" + modelFile + "', 'showProgressDialog', 'false'], process=[false]"); And in order to make the command run, you need to install StarDist from its update site. But I cannot test because I don’t have Tensorflow install…

Side topic: Is it maybe time to discuss how to call Ops from macro?

I hope that helps.

Cheers,
Robert

[Christian_Tischer]

@haesleinhuepf

comes via StarDist update site

Looks interesting! Any ideas (@frauzufall) whether this functionality would be part of core Fiji at some point?

[haesleinhuepf (Robert Haase)]

Hey @Christian_Tischer,

how about we put it in ImageJ-legacy without bothering @frauzufall?

Would you mind sending a PR?

Thanks!

Cheers,
Robert

[imagejan (Jan Eglinger)]

@haesleinhuepf

Is it maybe time to discuss how to call Ops from macro ?

Unpopular opinion: is it maybe time to stay away from macro language altogether, and make the more powerful scripting languages easier to use for newbies, instead of implementing yet another workaround to the limitations of macros?

---

Joking aside: I really like your pragmatic approach to build bridges for really everybody.

Ops currently have a few wrinkles that make them overly complicated, and almost impossible to use without any knowledge of ImgLib2 API. Maybe we can work as a community on improving the situation here? Also, there’s scijava-ops around the corner, so the situation might improve soon.

[haesleinhuepf (Robert Haase)]

@imagejan

make the more powerful scripting languages easier to use for newbies

Joking aside: How can we achieve this? I’m definitely on board for making this happen, e.g. by improving auto-complete, documentation and interoperability.

And I believe, honestly, what we need the most is a strategy: What’s most important for the community of users? What’s most important for developers? How can we balance both?