Write convenience functions for plugin handling

[raacampbell]

• [ ] Make a method that produces a list of installed plugins and asks the user to pick one and returns the picked plugin. Can make this from code in the plugin remover.
• [ ] Integrate the above into the plugin remover and plugin updater.
• [ ] Add a method that will check all installed plugins for a latest version and print to screen whether a new version exists.
• [ ] Add an "update all" method

[alexanderbrown]

As a suggestion - what about a centrally maintained list of known masiv plugins so that people can find them? This could even be automated in to the plugin manager

[raacampbell]

So we could add the list of plugin URLs to a text file that is read by the plugin manager. Then we add an availablePlugins method that scans the list and reports what's available on the web. The list can have flags for whether a plugin is installed or whether it is out of date. Something like that?

[alexanderbrown]

Yeh that sounds like it. Relatively simple but quite useful On Sat, 7 Jan 2017 at 16:03, Rob Campbell notifications@github.com wrote:

So we could add the list of plugin URLs to a text file that is read by the plugin manager. Then we add an availablePlugins method that scans the list and reports what's available on the web. The list can have flags for whether a plugin is installed or whether it is out of date. Something like that?

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/alexanderbrown/masiv/issues/4#issuecomment-271091980, or mute the thread https://github.com/notifications/unsubscribe-auth/AFH45Qb5PY8nsgX3ngqV4BcEo2pQDRykks5rP7dpgaJpZM4LafYb .