Req alternative to prevent abuse of <requires> in addon.xml
#24
(2015-09-28, 18:17)im85288 Wrote: Very nice, reading back over the thread it was me that refused to remove the next up addon from my mod. The way I see it is that users will not know it exists if it is not auto installed. I added an option to the addon to disable it for users who prefer not to use it (same as tvtunes) You cannot expect the average user to know that this addon exists so I will continue with that format. The real issue is Kodi does not allow it to be disabled/uninstalled which is frustrating.

Well even though you could disable it it's quite an adventure for the user to go find the add-on that is causing a certain behaviour. I personally wouldn't want a bunch of add-on being installed even though i could disable them.

Take "Next Up". Say you install this by default, how will the user know what he needs to disable to get rid of that behaviour?
Same could be said for TV Tunes or whatever add-on. Sometimes the name of the add-on is not to clear on what it does.

I'm not saying we shouldn't allow disabling of "default" dependencies but even allowing them brings problems. Next one is what is skin critical and which one is not? I would call skin shortcuts critical but script.language not. It's a point of view you take. Some might find the weather addon absolutely critical or subtitles.
It's a difficult item to get right.
Read/follow the forum rules.
For troubleshooting and bug reporting, read this first
Interested in seeing some YouTube videos about Kodi? Go here and subscribe
Reply


Messages In This Thread
RE: alternative to prevent abuse of <requires> in addon.xml - by Martijn - 2015-09-28, 19:06
Skin "REQUIRING" Addons. - by TwistedFaith - 2015-11-07, 10:57
Logout Mark Read Team Forum Stats Members Help
alternative to prevent abuse of <requires> in addon.xml0