MCML Layout

Yup, that's a scaled down fanart.  That layout is correct (but the details under will be the episode details - not show details - thats just a mockup - but i acutally have the MCML working other than the silly selection bar)  But it is very close to how i want it to look.

All the data is retrieved from thetvdb.com including the fanart.  The data is stored in a MS SQL CE database (though i am using a provider model so i could easily add a different storage backend).  I already wrote a companion app that can be used to manage the metadata.  It can scan for wtv files or any other file type (as long as i write a class to do it).  It's also a centralized database - so you can use multiple devices to provide content if you want.

As far as testers - i am still a ways off.  But i will post back here when i am ready for that.

Thanks for the help.  I still will probably need some help, so ill post back here when that happens.  PS - i think i use a service you wrote to scrape themoviedb.org for xbmc nfo files.

Hi Michael,

I am working an a project for WMC that grabs schedule data for premium channels, goes out to rotten tomatoes (via api), and selects movies to record based on filter criteria, sets up the recording, moves the file to a server.  Then there are 3 UI screens (Library, Scheduled to Record, Scheduled to Skip).  Obviously, it's more complicated that that, but that is the basic idea.

Everything seems to be all set, but i am getting the guide data in a way that violates the content provider TOS, so i cant distribute the program.  Do you know a decent way to get guide data?  You are doing it somehow for companion services, right?  I looked into using the provider for Myth, but it costs money now.