home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 2
Submit: Code Patches
Port SlimTv to MPExtended
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Oxan" data-source="post: 826225" data-attributes="member: 97484"><p>The current TV client in MP2 uses TV4Home Core Service, on which development has halted. The <a href="https://forum.team-mediaportal.com/webservice-mobile-access-537/mpextended-service-0-4-a-103873/" target="_blank">MPExtended Service</a> is it's successor. The API changes in the TV part are fairly minimal, and consist of only a few renamed properties. While the MPExtended API isn't frozen yet the part MP2 uses won't change anymore. Given this situation, I think it's a good idea to migrate the TV client to the MPExtended service. </p><p></p><p>I've pushed a patch for this to my <a href="https://github.com/oxan/MediaPortal-2/tree/MPExtended-instead-of-TV4Home" target="_blank">fork on GitHub</a>. It consists of two parts:</p><ul> <li data-xf-list-type="ul"><a href="https://github.com/oxan/MediaPortal-2/commit/63f9cb054edfe2ef54c7c67876a0809988a1b5a9" target="_blank">Change the SlimTv4HomeProvider to the new MPExtended API</a>. </li> <li data-xf-list-type="ul"><a href="https://github.com/oxan/MediaPortal-2/commit/b83b5437bfa08482acd55958cdd3b8aaad2e2abd" target="_blank">Rename SlimTv4HomeProvider to SlimMPExtendedProvider</a>. This part isn't really required but I think it'll confuse people if the old name is kept. </li> </ul><p></p><p>I haven't actually tested these changes yet (just compiled them), but I don't think they'll break anything. </p><p></p><p>I also found the folder Incubator/TV4Home, but I don't think it's being used anymore. Let me know if I should update that one too.</p></blockquote><p></p>
[QUOTE="Oxan, post: 826225, member: 97484"] The current TV client in MP2 uses TV4Home Core Service, on which development has halted. The [url=https://forum.team-mediaportal.com/webservice-mobile-access-537/mpextended-service-0-4-a-103873/]MPExtended Service[/url] is it's successor. The API changes in the TV part are fairly minimal, and consist of only a few renamed properties. While the MPExtended API isn't frozen yet the part MP2 uses won't change anymore. Given this situation, I think it's a good idea to migrate the TV client to the MPExtended service. I've pushed a patch for this to my [url=https://github.com/oxan/MediaPortal-2/tree/MPExtended-instead-of-TV4Home]fork on GitHub[/url]. It consists of two parts: [LIST] [*][url=https://github.com/oxan/MediaPortal-2/commit/63f9cb054edfe2ef54c7c67876a0809988a1b5a9]Change the SlimTv4HomeProvider to the new MPExtended API[/url]. [*][url=https://github.com/oxan/MediaPortal-2/commit/b83b5437bfa08482acd55958cdd3b8aaad2e2abd]Rename SlimTv4HomeProvider to SlimMPExtendedProvider[/url]. This part isn't really required but I think it'll confuse people if the old name is kept. [/LIST] I haven't actually tested these changes yet (just compiled them), but I don't think they'll break anything. I also found the folder Incubator/TV4Home, but I don't think it's being used anymore. Let me know if I should update that one too. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
Submit: Code Patches
Port SlimTv to MPExtended
Contact us
RSS
Top
Bottom