![]() My first goal would be to get everything working as well as the current integrated solution along with UI support. The path for the schedules direct classes would be. ![]() I would leave the Gson code otherwise unchanged so we could upgrade it if the need were to arise without any serious complications. I will just take the parts we need and change the root class path to .gson so it doesn't conflict with any plugins. ![]() We should also be able to eliminate some library dependencies that we would otherwise need to account for to use the plugin code.įor the JSON parsing, I propose that we use Gson since it's owned by Google already and a compatible license. Re-writing this EPG service will result in it being written as a piece of the core, using all that is available internally and not something that is somewhat disconnected. I have been looking at doing this over the past few weeks and I think it would be best to build everything from the ground up instead of using the plugin. It needs to be selectable and configurable within the UI. Schedules Direct needs to be a first class citizen fully integrated into SageTV. This is one of the barriers to entry for new SageTV users. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |