Reply to thread

Message

<blockquote data-quote="Tony Wall" data-source="post: 1087747" data-attributes="member: 125233">Yes I know it's not perfect, but the last version at least has the episode information which is more critical than the extra &quot;click here for more information&quot; text you can ignore or edit out.The first problem with creating WebEPG templates is beyond the simplest sites you can no longer use the WebEPG Designer. It can't be extended either because there is no source available, only for the grabber/TV service plug-in. The main problem though is the templates whilst nice for simple examples are too hit-and-miss, e.g. have inconsistent start/end/newline/whitespace handling.With EPG providers, I feel if you're lucky enough to be allowed to read data directly (XMLTV or JSON) then you don't need WebEPG anyway (use the more standard XMLTV). So the only purpose of WebEPG I see is for forcefully extracting data (&quot;screen scraping&quot;). Good... but this is exactly the area where it is weak.Anyway I will complete what I started in a few weeks. I've got a lot of ideas in this area but they are so different they will be a different thing altogether. I agree EPG is essential but unfortunately also a big pain.If you want to play, try editing the template yourself. You'll need my DLL else you won't event be able to request any data. That was the main fix, good for any template. Just be careful to double-check each time you think it's working (e.g. extra text gone) as you'll most likely find other parts suddenly drop-out (sometimes only a few channels so be thorough). It' a nightmare without a proper GUI or unit test to step-through with a debugger.[DOUBLEPOST=1403548290][/DOUBLEPOST]Import/merge channels is also a grey area in the current code vs GUI options. That will be included in the unit tests I write so potentially improved soon.</blockquote>

[QUOTE="Tony Wall, post: 1087747, member: 125233"] Yes I know it's not perfect, but the last version at least has the episode information which is more critical than the extra "click here for more information" text you can ignore or edit out. The first problem with creating WebEPG templates is beyond the simplest sites you can no longer use the WebEPG Designer. It can't be extended either because there is no source available, only for the grabber/TV service plug-in. The main problem though is the templates whilst nice for simple examples are too hit-and-miss, e.g. have inconsistent start/end/newline/whitespace handling. With EPG providers, I feel if you're lucky enough to be allowed to read data directly (XMLTV or JSON) then you don't need WebEPG anyway (use the more standard XMLTV). So the only purpose of WebEPG I see is for forcefully extracting data ("screen scraping"). Good... but this is exactly the area where it is weak. Anyway I will complete what I started in a few weeks. I've got a lot of ideas in this area but they are so different they will be a different thing altogether. I agree EPG is essential but unfortunately also a big pain. If you want to play, try editing the template yourself. You'll need my DLL else you won't event be able to request any data. That was the main fix, good for any template. Just be careful to double-check each time you think it's working (e.g. extra text gone) as you'll most likely find other parts suddenly drop-out (sometimes only a few channels so be thorough). It' a nightmare without a proper GUI or unit test to step-through with a debugger.[DOUBLEPOST=1403548290][/DOUBLEPOST]Import/merge channels is also a grey area in the current code vs GUI options. That will be included in the unit tests I write so potentially improved soon. [/QUOTE]

Verification