improve fiji search bar result

[k-dominik]

right now users have to know the term "Pixel Classification" to get to this command via the search. Putting in "ilastik" and then getting all the possible commands would be nice.

Without breaking backwards compatibility of course.

[imagejan]

That is: the search should also display commands where only the menu name matches (maybe with lower priority than direct matches), right?

Looks like an issue for https://github.com/scijava/scijava-search/issues, maybe @haesleinhuepf has a quick idea how to solve it.

[haesleinhuepf]

Hey all,

yes, unfortunately the Fiji search only searches in the menu name, not in parent menus. That's why I'm used to write long menu entries so that many search item hit.
Short term solution:

• Rename your plugin menu entry to "ilastik Pixel Classification" and
• make a copy with the old name. Put it in a 'Deprecated' sub menu. That's state of the art I'd say.
  

Long term solution:

• We should tag our plugins to categorize them. We might also find an automated way of setting some tags. E.g. a plugin with "Threshold" in its name can safely go to a "Segmentation" category. Last but not least: I'd say some plugins should appear in several menus. The "ilastik Pixel Classification" should for example show up in "Segmentation". Some other plugins (like the deprecated ones) should not appear in any menu and still be callable. But maybe that doesn't belong here ;-)

Cheers,
Robert

[k-dominik]

Hey @imagejan and @haesleinhuepf,

thank you very much for your replies. Your workaround, Robert, sounds like a sound solution to our problem. 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?

But as you mention tags would feel more natural, or any kind of other hidden annotation that would only be visible in the search bar.

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

Cheers and thanks again :)

Dominik

[haesleinhuepf]

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

[k-dominik]

has this been silently, sneakily improved? I now get everything I want to see when typing in "ilastik":

in any case, this issue can be closed with that kind of behavior...