Flow.Launcher icon indicating copy to clipboard operation
Flow.Launcher copied to clipboard

Install plugins directly from the Plugin Store

Open mrx23dot opened this issue 2 years ago • 7 comments

  • I select addon
  • Click on install That should be enough.

But instead it shows internal install command, plus assumes that I know that have to click again.

2023-04-25_214923_RC

mrx23dot avatar Apr 25 '23 20:04 mrx23dot

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] avatar Jun 10 '23 01:06 github-actions[bot]

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] avatar Jul 27 '23 01:07 github-actions[bot]

This issue was closed because it has been stale for 7 days with no activity. If you feel this issue still needs attention please feel free to reopen.

github-actions[bot] avatar Aug 03 '23 01:08 github-actions[bot]

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] avatar Sep 18 '23 01:09 github-actions[bot]

I think the same applies for uninstalling, if you click on a plugin in the settings under plugins, then it is also first entered in the searchbar and then you have to confirm a dialog.

flooxo avatar Feb 01 '24 16:02 flooxo

This is more of a design issue with flow. PluginsManager plugin was introduced before the Store, which moved all functionalities related to handling plugins into a single plugin. Plugin Store came and the first cut was to piggyback off it that's why it still leads to the PM plugin code.

Going forward I think it makes sense to either move all plugin management functionalities to the API so others can build their own plugin manager, or move them back into the core project with the code for Store.

jjw24 avatar Feb 04 '24 07:02 jjw24

This is more of a design issue with flow. PluginsManager plugin was introduced before the Store, which moved all functionalities related to handling plugins into a single plugin. Plugin Store came and the first cut was to piggyback off it that's why it still leads to the PM plugin code.

Going forward I think it makes sense to either move all plugin management functionalities to the API so others can build their own plugin manager, or move them back into the core project with the code for Store.

While making #2369 I've moved install logic to Core.PluginManager.

VictoriousRaptor avatar Feb 12 '24 02:02 VictoriousRaptor