Search results

{{mininav|[[Development]]|[[Add-on development]]}} === Submitting a Compliant Add-on to the Kodi.tv Repo ===

...g up the slide in submenu (press left {{keypress|left}} to show/hide). The Add-on manager is not where you go to run add-ons, but only to install and configu == How to access the Add-on browser ==

{{mininav|[[Development]]|[[Add-on development]]}} ...epository, it can published to our official repository if submitted by the add-on developer. Add-ons can also be published in other repositories or as stand

{{mininav|[[Development]]|[[Add-on development]]}} ...ode>addon.xml</code>) reside in the "root" of the folder that contains the add-on. Additional data may be contained within a <code>resources/</code> subfold

...r version 18 of Kodi, just as "Krypton" was the codename for Kodi v17 and "Jarvis" was the codename for Kodi v16. You will often see "v18" and "Leia" used i ...hon 3 interpreter (plus enforcing Python 2 & 3 compatibility in Leia addon repository)<ref>https://kodi.tv/article/attention-addon-developers-migration-python-3<

{{Mininav|[[Development]]|[[Add-on development]]}} ...n how this file is structured and which elements must be used to create an add-on for Kodi. You can also consult the examples at the end to see how this file