(2013-12-19 01:00)xnappo Wrote: Honestly I am not all that clear on this either. I have mostly been looking at Aeon Nox. It is very sparsely commented and has all sorts of logic to figure out what to display. Most of the variables it checks are not things I can set from the Python side. I believe that in the 'normal' XBMC library these are stored in the videodb. However when I am generating the file list from Python, I am creating the objects on-the-fly and setting various properties. It seems like at least Aeon Nox is expecting the info to only come from the videodb for some things.
If you look at the PleXBMC thread here and over at the Plex forum (the XBMC addon thread) you will see them having this same conversation a year ago They made skin mods to make PleXBMC work better - however the whole project seems to have splintered quite a bit...
Well, I kind of saw some of this discussion, but since it was tl;dr or at least "too long didn't read it completely" I thought they ended up needing their skins to support PMS recently added and "on deck" items.
If you are able to set info and MB3 server is creating nfos, then I'd think that the xbmc videodb may be able to take care of itself. I don't know enough about either's video database management underpinnings to begin to understand what will make the best "glue" for these to stay in sync.
While I keep getting off track, your progress on this is fantastic. With a little tweaking, I think this could quickly render MB3 server "usable" to OpenELEC clients (including RPi) much faster than a port of MBT will be generated for those platforms.
Also, from someone who's just started looking into skins and skin mods, MQ5 is easier for me to follow than Nox