United States of America
Started on: 2007-10-16
last update: 2007-10-16
Summary:
Revamp code and database to provide a way to allow users to easily write a .dll that can be used to control unsupported hardware. (R5000-HD, etc)
Description:
I was looking at the code, trying to trace everything out in hopes of adding support for the R5000-HD hardware modifications done by Nextcomwireless. I found it a bit daunting.
I was thinking, why not revise the code and implement a Factory type model for tuners. You would have all the implementation specific code for a tuner type (ATSC, DVB, IPTV, QAM, Custom, etc) inside its respective dll (aka MediaPortal.Tuners.ATSC.dll, MediaPortal.Tuners.DVB.dll, etc). In the database, just specify the name of the class and .dll for each tuner and load it at runtime.
Adding support for some future device could be as simple as inheriting from a base class, overriding a couple methods, adding the tuner to the database and which dll should be used.
This could be extended out to include channel changing support. The tuner entry in the database would have a field that named the .dll for the tuner and the .dll for channel changing.
This would add a great deal of flexibility to the TV configuration and it would easily allow other people to create tuner "plugins".
Cheers!
Randell
last update: 2007-10-16
Summary:
Revamp code and database to provide a way to allow users to easily write a .dll that can be used to control unsupported hardware. (R5000-HD, etc)
Description:
I was looking at the code, trying to trace everything out in hopes of adding support for the R5000-HD hardware modifications done by Nextcomwireless. I found it a bit daunting.
I was thinking, why not revise the code and implement a Factory type model for tuners. You would have all the implementation specific code for a tuner type (ATSC, DVB, IPTV, QAM, Custom, etc) inside its respective dll (aka MediaPortal.Tuners.ATSC.dll, MediaPortal.Tuners.DVB.dll, etc). In the database, just specify the name of the class and .dll for each tuner and load it at runtime.
Adding support for some future device could be as simple as inheriting from a base class, overriding a couple methods, adding the tuner to the database and which dll should be used.
This could be extended out to include channel changing support. The tuner entry in the database would have a field that named the .dll for the tuner and the .dll for channel changing.
This would add a great deal of flexibility to the TV configuration and it would easily allow other people to create tuner "plugins".
Cheers!
Randell
