When you say you tend to add very long entries to your menus, do people complain when using macros about those long names? Or is everyone copy-pasting the macro-recorder output anyway?

Very interesting question. I was engineering user experience here as well by using macro extensions. After clicking the menu "Add image and scalar on GPU", this gets recorded:

run("CLIJ2 Macro Extensions", "cl_device=[gfx902]");

// add image and scalar
image5 = "Untitled";
Ext.CLIJ2_push(image5);
image6 = "add_image_and_scalar-249372081";
scalar = 1.0;
Ext.CLIJ2_addImageAndScalar(image5, image6, scalar);
Ext.CLIJ2_pull(image6);

At the beginning people are a bit shocked but they quickly get used to it, because it's actually easier to read than all parameters combined as a string with[] and= in between.

I'd say Macro-Extensions don't make much sense when you have a single individual plugin. However, if you plan to offer more functionality to ilastik4ij users, it might be a way to go. They are not very popular among developers because you handle your parameters as an Object[] array. But users love it. Again, because it's not a string with operations inside. Oh and, auto-completion makes sense than as well - especially as it bring documentation to the users eye and also a link to the developers website, for example.

I wrote a blog-post about how build Macro-Extensions for your plugins. The recording-part is missing yet. If you go down that road, I'll write that part for you and for the public ;-)
https://haesleinhuepf.github.io/extend-macro-autocompletion

would you guys mind if I open an issue about it with https://github.com/scijava/scijava-search/issues ?

Great idea! Go ahead :-)

Thanks!

Cheers,
Robert

improve fiji search bar result #61

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions