2014-10-14, 20:36
Note: this is a c/p from our internal team forum about add-on manager improvements
As already started by jmarshall in https://github.com/xbmc/xbmc/pull/4287
Suggestions
Add-on manager changes:
- Enable/disable auto-updates always/notify/never per repo
Use case: allow XBMC.org repo to auto update but dev or 3rd party repos not.
Perhaps allow minor patch updates to auto-update. x.y.Z versions
- Disputable set to notify by default. My suggestion would be to ask the user on first use of XBMC and on install of every extra repo he installs what default action should be. Current auto-update options is to hidden to be obvious.
- Restructure add-on manager tree as show in http://addons.xbmc.org/ to simplify layout
alternative layout
- Show modules as separate category as "support modules" (see layout)
- Add "all add-ons" entry that will show all installed add-ons
- Add history list sorted by last updated add-on
- Add warning when installing repo/add-ons through .zip for possible implications
- Remove the side panel or better explain the available options there
- Improve general GUI layout. Perhaps use same layout as is used for the settings categories.
Keep the category on the left visible and show available add-ons on the right side.
Skinners please brainstorm about this.
- Add advanced search/filtering same like done in library. To search by title, description, repo, author, language.
- Add Geo-block option like once started https://github.com/xbmc/xbmc/pull/829
- hide the broken/incompatible ones by default.
- Semi related: Rip skin settings out of guisettings.xml and do it like regular add-ons.
Any remarks/suggestions so this show can hit the road?
Perhaps non developers are interested in taking this job
As already started by jmarshall in https://github.com/xbmc/xbmc/pull/4287
Suggestions
Add-on manager changes:
- Enable/disable auto-updates always/notify/never per repo
Use case: allow XBMC.org repo to auto update but dev or 3rd party repos not.
Perhaps allow minor patch updates to auto-update. x.y.Z versions
- Disputable set to notify by default. My suggestion would be to ask the user on first use of XBMC and on install of every extra repo he installs what default action should be. Current auto-update options is to hidden to be obvious.
- Restructure add-on manager tree as show in http://addons.xbmc.org/ to simplify layout
PHP Code:
System->Add-ons->
* Disabled Add-ons
* Enabled Add-ons
* Get Add-ons
_* All Add-ons
_* XBMC.org repository
___* Audio
___* Information providers
____* Lyrics
____* Subtitles
____* Metadata (or all these just one level down)
______* Artists
______* Albums
______* Movies
______* Music videos
______* Support modules (scraper modules)
______* TV-Shows
______* Weather
___* Games (add as future requirement)
___* Pictures
___* Programs
___* PVR
___* Repositories
___* Services
___* Screensaver
___* Skins
___* Support modules (python/skin art)
___* Video
___* Webinterface
* Install from .zip
* Search
alternative layout
PHP Code:
System->Add-ons->
* Disabled Add-ons
* Enabled Add-ons
* Install from .zip
* Install from repository
_* All repositories
_* XBMC.org repository
___* Audio
___* Information providers
____* Lyrics
* Search all repositories
- Show modules as separate category as "support modules" (see layout)
- Add "all add-ons" entry that will show all installed add-ons
- Add history list sorted by last updated add-on
- Add warning when installing repo/add-ons through .zip for possible implications
- Remove the side panel or better explain the available options there
- Improve general GUI layout. Perhaps use same layout as is used for the settings categories.
Keep the category on the left visible and show available add-ons on the right side.
Skinners please brainstorm about this.
- Add advanced search/filtering same like done in library. To search by title, description, repo, author, language.
- Add Geo-block option like once started https://github.com/xbmc/xbmc/pull/829
- hide the broken/incompatible ones by default.
- Semi related: Rip skin settings out of guisettings.xml and do it like regular add-ons.
Any remarks/suggestions so this show can hit the road?
Perhaps non developers are interested in taking this job