this is just to confirm i understand the process around addons and skins
- the same process applies to skins and to addons
Yes, pretty much, when choosing skin few more fileds(like colors, theme... these optional fields) will show up(haven't implemented it yet, WIP), as for other kinds of addons, yes those will be the all of the process.
- a developer creates a topic on the forum for their initial skin/ addon
- 1) the forum add-on version can go through a number of iterations on the forum
- when the developer feels the skin/ addon is ready, he can use this dashboard submit the skin/addon
Yes, this is the process i am targetting
- question: does an admin(/ moderator?) need to give that user any permissions beforehand or can anyone submit a skin/ addon?
When you go to dashboard you can see your rank there, for now there are four ranks, Admin, Mod, Elite, Newbie
For Newbie users, they can add/update addon BUT admin/mod have to review and allow it, admin/mod can allow it through dashboard(WIP).
For Elite User they can add or update any addon as they fit.
WHEN a newbie users has atleast of 5 addon(could be any category skin, visualizer, plugins, theater mode but Equalizer does not count) on their dashboard, they will be able to add/update addons easily.
For Elite rank, you need atleast 20 addon(equalizer does not count) to get that rank.
All these 5 addon, 20 addon requirement is a example, you can suggest me the amount that required. It is just an example of how the system works.
- then an admin(/ moderator) accepts the submission so it now appears on the main web-site Skin/ Addons link
- if further changes are made, then the steps from 1) are repeated
If the user updates the addon but does not have more that 5 addon, mods/admin will need to re-allow them.
Alternatively, if a member is trusted, but doesn't have 5 addons, admin (only admin) will be able to remove this restriction from their profile.
- i noticed a "Reported Issues" link - how do you see that working? I would have thought that reporting issues on the forum topic would be best for that
Yes, it will get removed in next update, forum will be used as default issue reporting place.
Right now it serves me as a debug page
- this is where i am quite hazy - you mentioned about linking the Addon(/ skins?) to a major musicbee version. Could you explain this some more
- as a FYI: i try to make sure all MB versions are backwards compatible with old plugins. For v3, there are a couple of my last.fm plugins that will break and need a new version. But thats the exception rather than the rule. For skins, although they wont break with v3,a number wont work very well. I'm not sure we need to tie skins to major MB versions
Here is the idea behind the major version idea:
When most software gets major updates, things brake, skins will have rendering glitches, some plugin might not work/unstable, and those older skins/plugins won't support the latest api or changes for the musicbee.
And what happens when a addon uses the latest api, but the end user have a older musicbee version, things wont work properly.
And this creates quite a bit of problem for end user. When you add a major musicbee update to admin panel it will be automatically added on dashboard, devs can target those latest major changes(using the new api, or panels) and also let the user know what major version needed for it to work.
OFC, devs will be able to choose any amount of musicbee version, if their skin/addons works with all of them.
You can remove any MusicBee version from the dashboard by going to all musicbee release
tab in the admin panel and edit them(unchecking the dashboard availability).
The main reason for this is to better maintainability for FUTURE. OFC devs can also add a important note in the dashboard of their addon, if any confusion appears.(which i forgot to add in the demo