Plugin Store

[onesounds]

Load https://github.com/Flow-Launcher/Flow.Launcher.PluginsManifest when open setting,

• Load https://github.com/Flow-Launcher/Flow.Launcher.PluginsManifest when choose plugin store tab.
• Managing in setting window.
• user can found easily new plugin and updates.
• The command line installation method (pm install) remains the same.

Why

• Installable, all plug-in lists should be visible at a glance.

Additional considerations

• This may require a refresh button. (list update check)
• What if there are more than 30 plug-ins? Wouldn't there be a heavy load?
• It would be nice if you could receive icons when you receive the list.

ETC

• I considered the idea of integrating with the plug-in tab, but we'd better distinguish between setting management/installation.

Done. #740

[Zeroto521]

That's a good idea for users.
Easily know and get plugins, no more type command just browse and click.

I just have a problem with the store.
For now, we only have 20+ plugins. Such a number of plugins could be list here. But when the number grows up, how to find a plugin that you want would be a problem.

[onesounds]

Good Point, There should be page control.
Or I think it would be okay to make it first, and make it again when it exceeds 50. 😂

[deefrawley]

What about a search function here?

[onesounds]

What about a search function here?

I don't think it's essential, but I think it'd be nice to have it.

[red9350]

The plugin store could have 2 tabs:
"Installed" only shows the currently installed plugins, and has a "Check for updates" button;
"Available" shows all the plugins present in the repo, minus the ones already installed;

Both tabs should have a search bar

[taooceros]

@jjw24 should we migrate some functionality in pluginsmanager plugin to built-in project? like the pluginsmanifest, and let it be accessed via ipublic api or something else.

[jjw24]

lets just convert PluginsManager into the Plugin Store's backend code, this is probably the easiest

[jjw24]

hmm do we then lose the ability to use it via the query?

[taooceros]

hmm do we then lose the ability to use it via the query?

Not really. We can still have a plugin project link to the manifest project I guess.

[jjw24]

Sorry what do you mean by link?

[taooceros]

Oh I mean we can let the plugin one reference to the built-in project.

[onesounds]

#740 done