Reply to thread

Message

<blockquote data-quote="James" data-source="post: 89650" data-attributes="member: 12681">Hi patrick,Thanks for your interest. I do plan to add detailed info the wiki, but until I find some time I will give you the details here.The start and end, are simply search strings to quickly filter out large parts of the html source. As sometimes the template it not totally unique on the page. Also can help speed the parsing on large pages.Ok the template is basically html tags and parser tagsAll html tags are supported, include comments &lt;!-- ---&gt;Parser tags are ones I invented for marking the place where the interesting data is. I have 3 at the moment &lt;#xxxx&gt; &lt;*xxxx&gt; &lt;Zxx&gt;.In this post I will just cover the major one &lt;#xxx&gt;A simple template would look like this:[CODE]&lt;tr&gt;&lt;td&gt;&lt;#START&gt;&lt;/td&gt;&lt;td&gt;&lt;#TITLE&gt;&lt;/td&gt;&lt;td&gt;&lt;/tr&gt;[/CODE]The parser searches for this pattern in the HTML source and reports the number of times it finds it.When you ask it to parse a certain occurance, it will get the text form the html source, located where the &lt;#START&gt; and &lt;#TITLE&gt; tags are and pass this into an IParserData object using the SetElement(string tag, string value) method. In this case tag = &quot;#START&quot; or &quot;#TITLE&quot; and value will be the text located in the html source at this location. Characters can be put in front and behind the &lt;#&gt; tags to remove part of the text.so &quot;-&lt;#START&gt;.&quot; will search for the '-' and '.' and pass what is between these as the value string into the SetElement method. To use more then one character in front and behind you need to use the following syntax &lt;#TAGNAME:front,back&gt;, where front and back are search strings (either can be empty). If no search strings/characters are given, then it will go to the next tag. Of cause extra parsing can be done in the IParserData object. You just need to create a new class with this interface.The tag names can be anything, and just need to be in your template and in the IParserData class must know what to do with them. I have made a very simple ParserData class which just stores the tag/value pair in a Dictionary, these can then be retreived by tag name later. This will take any tag and value pair.The WebEPG IParserData class however looks like this:[CODE]switch (tag)&nbsp; &nbsp; &nbsp; &nbsp; {&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; case &quot;#START&quot;:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; BasicTime startTime = GetTime(element);&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; break;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; case &quot;#TITLE&quot;:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; _title = element.Trim(' ', '\n', '\t');&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; break;...[/CODE]It does extra parsing of the element values, for example trimming the spaces and other junk or parsing the time values from strings.The Tags variable, tells the parser which HTML tags are interesting, all other tags will be ignored. It is the first character of the HTML tag name.So &quot;T&quot; = all table tags&quot;I&quot; = img &quot;D&quot; = div&quot;!&quot; = commentetc.I take all table tags as one group, mutliple tags can of course be given ie &quot;TSD&quot; (table, span, div), etc, etc.So in this example I would use &quot;T&quot; as all the tags are table tags (ie starting with the letter T). This means that the real HTML source could have other tags in it, but the parser would match it because it would just ingore these tags.General it to use a few tags as required to make the template unique to the data. Using too many tags can mean small changes require template changes. Such tags like table tags which define structure are good, because the structure doesn't often change. I hope this helps. I will try to get a start on the wiki documentation soon./James</blockquote>

[QUOTE="James, post: 89650, member: 12681"] Hi patrick, Thanks for your interest. I do plan to add detailed info the wiki, but until I find some time I will give you the details here. The start and end, are simply search strings to quickly filter out large parts of the html source. As sometimes the template it not totally unique on the page. Also can help speed the parsing on large pages. Ok the template is basically html tags and parser tags All html tags are supported, include comments  Parser tags are ones I invented for marking the place where the interesting data is. I have 3 at the moment <#xxxx> <*xxxx> <Zxx>. In this post I will just cover the major one <#xxx> A simple template would look like this: [CODE] <tr> <td><#START></td> <td><#TITLE></td> <td> </tr> [/CODE] The parser searches for this pattern in the HTML source and reports the number of times it finds it. When you ask it to parse a certain occurance, it will get the text form the html source, located where the <#START> and <#TITLE> tags are and pass this into an IParserData object using the SetElement(string tag, string value) method. In this case tag = "#START" or "#TITLE" and value will be the text located in the html source at this location. Characters can be put in front and behind the <#> tags to remove part of the text. so "-<#START>." will search for the '-' and '.' and pass what is between these as the value string into the SetElement method. To use more then one character in front and behind you need to use the following syntax <#TAGNAME:front,back>, where front and back are search strings (either can be empty). If no search strings/characters are given, then it will go to the next tag. Of cause extra parsing can be done in the IParserData object. You just need to create a new class with this interface. The tag names can be anything, and just need to be in your template and in the IParserData class must know what to do with them. I have made a very simple ParserData class which just stores the tag/value pair in a Dictionary, these can then be retreived by tag name later. This will take any tag and value pair. The WebEPG IParserData class however looks like this: [CODE] switch (tag) { case "#START": BasicTime startTime = GetTime(element); break; case "#TITLE": _title = element.Trim(' ', '\n', '\t'); break; ... [/CODE] It does extra parsing of the element values, for example trimming the spaces and other junk or parsing the time values from strings. The Tags variable, tells the parser which HTML tags are interesting, all other tags will be ignored. It is the first character of the HTML tag name. So "T" = all table tags "I" = img "D" = div "!" = comment etc. I take all table tags as one group, mutliple tags can of course be given ie "TSD" (table, span, div), etc, etc. So in this example I would use "T" as all the tags are table tags (ie starting with the letter T). This means that the real HTML source could have other tags in it, but the parser would match it because it would just ingore these tags. General it to use a few tags as required to make the template unique to the data. Using too many tags can mean small changes require template changes. Such tags like table tags which define structure are good, because the structure doesn't often change. I hope this helps. I will try to get a start on the wiki documentation soon. /James [/QUOTE]

Verification