Reply to thread

Message

<blockquote data-quote="morpheus_xx" data-source="post: 1294050" data-attributes="member: 48495">See <a href="https://forum.team-mediaportal.com/threads/mp2-898-porting-mp2-to-net-6.140089/post-1293632" target="_blank">https://forum.team-mediaportal.com/threads/mp2-898-porting-mp2-to-net-6.140089/post-1293632</a> for information about TVE3.5 source codes and how we use them in MP2.For MP2 I have created a complete abstraction over the used TV engine, that's why we can support TVE3 embedded, TVE3 client of standalone service,&nbsp; TVE3.5, TvMosaic. All interfaces are below &quot;SlimTV&quot; namespaces and all backends/connectors implement those interfaces. This has the main advantage that we don't need to change the SlimTV.Client (this is the UI part in MP2), if we deal with other backends. This was my solution to make TV access generic. If you want to implement similar flexibility, you should to the implementation of SlimTV.Client for MP1.</blockquote>

[QUOTE="morpheus_xx, post: 1294050, member: 48495"] See [URL]https://forum.team-mediaportal.com/threads/mp2-898-porting-mp2-to-net-6.140089/post-1293632[/URL] for information about TVE3.5 source codes and how we use them in MP2. For MP2 I have created a complete abstraction over the used TV engine, that's why we can support TVE3 embedded, TVE3 client of standalone service, TVE3.5, TvMosaic. All interfaces are below "SlimTV" namespaces and all backends/connectors implement those interfaces. This has the main advantage that we don't need to change the SlimTV.Client (this is the UI part in MP2), if we deal with other backends. This was my solution to make TV access generic. If you want to implement similar flexibility, you should to the implementation of SlimTV.Client for MP1. [/QUOTE]

Verification