OK so maybe I was a little ambitous when I sat down at my PC after a few beers tonight and decided I'd have a play at using the boxee API to see how it worked.. but here is where I've got to so far.
On MAC OSX, the simpliest way to add a plugin locally is to use the global path, as then you don't need to edit the sources.xml file somwhere, e.g. my music plugin is in a directory at
Create a 128x128 png file and put in TEST/default.tbn
Create a TEST/Default.py file for your python code
Create a TEST/descriptor.xml as per http://developer.boxee.tv/app-descriptor/
To get started with that.. I went here:
Which allowed me to get hello world on screen, although for some reason with the "loading" spinner on top of it..
I went back to the boxee API, to try to understand how that built on the XBMC API, and I was able to "import mc" the python API listed on the boxee page and start replacing the print "DEBUG" with mc.LogDebug("DEBUG") or mc.LogInfo("DEBUG").
The debug output goes to
After getting through this, which does work, it was dawning on me that I think I was approaching this backwards, the "standard" way to develop boxee plugins appears to be to use the WindowXML format with embedded python against the specific onscreen controls, rather than python that embeds the creation of controls.. hopefully playing with this will make something that looks better and more consistent with the rest of boxee!
Also contrary to my first assumption that the descriptor type "skin" is not just about overriding look and feel, but appears possibly synonymous with application.
Anyone got any help tips for someone wanting to get started with this?