Germany
A few month ago, i wrote an EPG-Importer for the tv-software DVBViewer (have a look on: http://www.dvbviewer.info/forum/index.php?showtopic=15578 (german!)). The main idea behind this development was the generation of a separation between the transfer/preparation of imported EPG-data to the corresponding database and the delivery of EPG-Data from (different) "data-sources".
The benefits of this concept are:
- if somebody wants to develop a new importer for an epg-datasource (like xmltv, tvm clickfinder,..), he has only to develop the part of the EPG-data-acquisition. He dont need to know, how the epg-data becomes imported to the mediaportal/tvengine-database.
- the provided epg-data (supplied by one/many datasource-module/s) can be post-edited on the same way (example: add "Live: " in front of the program-title, if the live-flag of the imported program is set).
- many more...
What do you think about such a concept? Interested? What could be better in reflection to a use in MPs tvengine?
The benefits of this concept are:
- if somebody wants to develop a new importer for an epg-datasource (like xmltv, tvm clickfinder,..), he has only to develop the part of the EPG-data-acquisition. He dont need to know, how the epg-data becomes imported to the mediaportal/tvengine-database.
- the provided epg-data (supplied by one/many datasource-module/s) can be post-edited on the same way (example: add "Live: " in front of the program-title, if the live-flag of the imported program is set).
- many more...
What do you think about such a concept? Interested? What could be better in reflection to a use in MPs tvengine?