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 1
MediaPortal 1 Plugins
My IP TV Plugin
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="overture" data-source="post: 96699" data-attributes="member: 17689"><p>No, I didn't get your IM. Could you resend it?</p><p></p><p>In the meantime I'll explain what I meant by my plugin architecture.</p><p></p><p>Generally, there seems to be a lot of sites providing IP TV. If we limit ourselves, and implement this plugin based on one site then we limit the amount of channels that can be retrieved (unless we write another plugin - which obviously means we're back to square one with the segregated data issue).</p><p></p><p>So what I propose is that a core IP TV 'host' plugin is created. This will contain the relevant code to discover other 'mini-plugin' DLL's at runtime via reflection. </p><p></p><p>This means that a mini-plugin can be created for each site out there. These will implement a specific interface (which we will need to define) so that all the data provided by the mini plugins is presented to the host application in a standard way.</p><p></p><p>The structure would be:-</p><p></p><p>Core IP TV Host DLL Plugin</p><p> |</p><p> |</p><p> \/</p><p>Mini Plugin Interface</p><p> /\</p><p> |</p><p> |___viewtv.co.uk mini plugin DLL</p><p> |</p><p> |</p><p> |___wwitv.com mini plugin DLL</p><p> |</p><p> |</p><p> |___worldwidemediaproject.com mini plugin DLL</p><p> .</p><p> .</p><p> .</p><p></p><p>Then all we have to worry about is any duplicate channels and how the data is presented to the user.</p><p></p><p>I hope this makes sense. Let me know what you think.</p><p></p><p>Talk Soon.</p><p></p><p>Phil</p><p></p><p>ps. January would probably suit me best.</p></blockquote><p></p>
[QUOTE="overture, post: 96699, member: 17689"] No, I didn't get your IM. Could you resend it? In the meantime I'll explain what I meant by my plugin architecture. Generally, there seems to be a lot of sites providing IP TV. If we limit ourselves, and implement this plugin based on one site then we limit the amount of channels that can be retrieved (unless we write another plugin - which obviously means we're back to square one with the segregated data issue). So what I propose is that a core IP TV 'host' plugin is created. This will contain the relevant code to discover other 'mini-plugin' DLL's at runtime via reflection. This means that a mini-plugin can be created for each site out there. These will implement a specific interface (which we will need to define) so that all the data provided by the mini plugins is presented to the host application in a standard way. The structure would be:- Core IP TV Host DLL Plugin | | \/ Mini Plugin Interface /\ | |___viewtv.co.uk mini plugin DLL | | |___wwitv.com mini plugin DLL | | |___worldwidemediaproject.com mini plugin DLL . . . Then all we have to worry about is any duplicate channels and how the data is presented to the user. I hope this makes sense. Let me know what you think. Talk Soon. Phil ps. January would probably suit me best. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
My IP TV Plugin
Contact us
RSS
Top
Bottom