René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Allow SearchActions (i.e. buttons) to be present but disabled for certain search results","articleBody":"Currently, the `SearchActionFactory#supports` method is used to decide if a `SearchAction` is to be included in a result's actions:\r\n\r\nhttps://github.com/scijava/scijava-search/blob/6105bdd562ae8e36d4170143e5d654a38b757639/src/main/java/org/scijava/search/SearchService.java#L61-L70\r\n\r\n... and a button is added for each supported action:\r\n\r\nhttps://github.com/scijava/scijava-search/blob/6105bdd562ae8e36d4170143e5d654a38b757639/src/main/java/org/scijava/ui/swing/search/SwingSearchBar.java#L514-L534\r\n\r\n---\r\n\r\nIt would be nice to have the possibility to **always include** a button for a certain result type (e.g. `ModuleSearchResult`) but to **disable** it (i.e. show it greyed-out) according to the fulfillment of some additional requirements (e.g. if a specific module doesn't support a given input type).\r\n\r\nIMHO, indicating that a certain action is available in principle, but not for the currently highlighted item, would allow for a more consistent user experience.\r\n","author":{"url":"https://github.com/imagejan","@type":"Person","name":"imagejan"},"datePublished":"2018-01-05T10:31:22.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/4/scijava-search/issues/4"}