2013-01-14, 00:48
I am a developer willing to give a try in writing my 1st XBMC plugin (Music add-on that would connect to a radio website that hosts 4 stations and archive) , and am a bit lost what are the best suggested development practices. I have pretty decent software development background and I am familiar with Python, so I need specifics, not general basics.
I have installed XBMC on RaspberryPi Wheezy.
So I landed in this page http://wiki.xbmc.org/index.php?title=Add-on_development and it seems it will serve for a good starting point. However, I'd like to know if it is ok that I just create a new folder (ie, "plugin.audio.my.test") in ~/.xbmc/addons , scramble up some minimal set of files, and hope that XBMC will respect this entity as a new add-on? I'd like to connect to this add-on location via ssh from my development computer, while having the XBMC running and displaying on my TV set. I'd expect that I can see the results immediately after I have updated my python code (or other add-on files like icon and xml config files), so that the development-testing cycle is as short as possible. So perhaps I have to take into account some caching/reloading issues on the XBMC side?
I have installed XBMC on RaspberryPi Wheezy.
So I landed in this page http://wiki.xbmc.org/index.php?title=Add-on_development and it seems it will serve for a good starting point. However, I'd like to know if it is ok that I just create a new folder (ie, "plugin.audio.my.test") in ~/.xbmc/addons , scramble up some minimal set of files, and hope that XBMC will respect this entity as a new add-on? I'd like to connect to this add-on location via ssh from my development computer, while having the XBMC running and displaying on my TV set. I'd expect that I can see the results immediately after I have updated my python code (or other add-on files like icon and xml config files), so that the development-testing cycle is as short as possible. So perhaps I have to take into account some caching/reloading issues on the XBMC side?