Plugin Updater/Update Alerter

[mrad]

Sorry if this has been suggested already.

It'd be nice to stay in sync with the work plugin creators do to improve and fix their plugins based on community reports.

I propose an update system or an alerter that at the very least, can handle plugins (consider the main program with a "beta" mode switch).

This could be created as a forked process, on user approval, it can read the current MB state (e.g. playing), terminate the main mb process, update, then reload mb and resume state (the updater would handle installations and portable versions).

[ma_t14]

YES!!

+1

[redwing]

I'd rather like to see "Check Updates" button at the top of the Prefences/Plugins pane. Upon clicking on it, users get "Up to Date" or "Update Now" for each plugin and can decide what to update after checking out the corresponding forum thread. It's what Firefox does for its plugins and I think it's more suitable to MB's plugins than Chrome's one-click auto-update for all extensions.

[ma_t14]

Well, to be honest I misread the original post and was actually thinking it was talking about MusicBee, not its plugins. Personally I would give priority to that and then we can start talking about plugins 

[mrad]

and was actually thinking it was talking about MusicBee, not its plugins. Personally I would give priority to that and then we can start talking about plugins 

Actually, the main program is very easy to follow - so easy that I suspect an updater would be dismissed as too trivial. However, the variety of available plugins are such that it's far more work to maintain those from a users perspective and way too easy to fall behind on new releases/fixes. Tackle the bigger issue first - then the smaller main program is a simple addition afterwards.

@Redwing you are on a creative line of thinking

[psychoadept]

This actually sounds like good fodder for a plugin itself.  But how would it figure out whether has a plugin has been updated in the first place?