Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Search bar improvement, add annotations/tags to plugins #19

Open
k-dominik opened this issue Jul 29, 2020 · 4 comments
Open

Search bar improvement, add annotations/tags to plugins #19

k-dominik opened this issue Jul 29, 2020 · 4 comments

Comments

@k-dominik
Copy link

The search bar is an incredibly useful feature - it made Fiji accessible for me 🎉

However, when I look e.g. at our ilastik4ij plugin, i'll have to add a small "but" to the praise above. The search bar will only show results that correspond to menu entries. For our plugin, one menu is ilastik -> run Pixel Classification. Now, only when a user types "Pixel Classification" she will get the correct result. I on the other hand would try "ilastik" as a search term first, and this command doesn't come up. There is a related discussion here: ilastik/ilastik4ij#61.

I'll quote @haesleinhuepf to make a suggestion for improvement:

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 ;-)

cc @haesleinhuepf @imagejan

@haesleinhuepf
Copy link
Member

Hi all,

just adding an idea from Martin Jones on twitter:
https://twitter.com/martinjones78/status/1288392449438744577?s=20

We could read the tags from NEUBIAS BIII database. Many popular plugins should be tagged in this database already.

Cheers,
Robert

@haesleinhuepf
Copy link
Member

See also:
#18

@ctrueden
Copy link
Member

ctrueden commented Sep 5, 2020

Thanks for the feedback, @k-dominik. I think the search could be improved to make ilastik match the run Pixel Classification plugin without needing to add support for tags: if the string is also matched against non-leaf menu strings, that would do it. I can't remember whether this is already the case, but it would also be good to match against descriptions too (i.e. the description = "..." part of the @Plugin annotation). So then you could add some description for the command that also uses the string ilastik, to ensure a match.

CC @frauzufall

@k-dominik
Copy link
Author

this seems to be fixed?!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants