Make resource content available via api? Make sense? Application examples please - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Development (https://forum.kodi.tv/forumdisplay.php?fid=32) +--- Forum: Add-ons (https://forum.kodi.tv/forumdisplay.php?fid=26) +--- Thread: Make resource content available via api? Make sense? Application examples please (/showthread.php?tid=343428) Pages:
1
2
|
RE: Make resource content available via api? Make sense? Application examples please - chrissix666 - 2019-05-01 (2019-05-01, 03:39)rmrector Wrote: Ya, and FWIW I don't think studio images are well suited for resource add-ons either, but the images are small and it's much better than the previous alternative - many skins used to include their own large collection of studio images, with a bunch of duplicates across them.agree! Quote:I do suggest they be provided from an API instead.But how should to integrate/implement? There is still a lack of a concept. Ideas? Quote:For the short term I think the current resource add-on could be simplified to one big zip that is just extracted to a folder, then point a skin setting to that folder instead of the resource add-on. While this collection is still changing rapidly, update zips can be posted that contain new and updated images since the last zip, and it is easier to manually add or replace images in a shared folder than in Kodi's add-on directory.Good ideas! I myself could not do something like that. I am a bricklayer and not a programmer. I can only do a bit skinnng .xml. If you are interested, the project is yours. Any implementation with ArtworkBeef seems unlikely because ArtworkBeef is only for Artwork Types and not quite suitable for resource content, am i right? |