Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
guides:creating_webcomics [2011/12/10 14:28]
cyo [Compositing]
guides:creating_webcomics [2016/02/24 01:49] (current)
72.220.136.78 [WebComics]
Line 1: Line 1:
 ====== WebComics ====== ====== WebComics ======
  
-ComicRack supports WebComics (.cbw) files. With WebComics ComicRack can read comics directly from web pages and display them as if they where standard eComics (CBR, CBZ). WebComics can be exported to other formats. If the definition supports it, WebComics can update itself to add new pages (like for daily or weekly comics).+ComicRack supports WebComics (.cbw) files. With WebComics ComicRack can read comics directly from web pages and display them as if they were standard eComics (CBR, CBZ). WebComics can be exported to other formats. If the definition supports it, WebComics can update itself to add new pages (like for daily or weekly comics).
  
 ===== File Format ===== ===== File Format =====
Line 113: Line 113:
 </​code>​ </​code>​
  
-Or you can define the three parts separately (for example if they are very complex or contain the | delimiter in the regular expression):​+Or you can define the three parts separately (for example if they are very complex or contain the | delimiter in the regular expression). The general form of the Part element is: 
 + 
 +<code xml> 
 +<Part  
 +   ​MaximumMatches="​maximum returned matches"​  
 +   ​Reverse="​True/​False"​ 
 +   ​Sort="​True/​False"​ 
 +   ​AddOwn="​True/​False"​ 
 +   ​Cut="​regular expression">​regular expression</​Part>​ 
 +</​code>​ 
 + 
 +The Cut attribute allows to run a regular expression before the main regular expression is called. The main regular expression will only match on this result. 
 +This way you can also specify the additional attributes:
  
 <code xml> <code xml>
Line 119: Line 131:
   <​Compositing/>​   <​Compositing/>​
   <​Parts>​   <​Parts>​
-    <​Part>​regex for the image link</​Part>​+    <​Part ​MaximumMatches="​3"​ Sort="​True"​>regex for the image link</​Part>​
     <​Part>​regex for the next page link</​Part>​     <​Part>​regex for the next page link</​Part>​
   </​Parts>​   </​Parts>​
Line 153: Line 165:
 The scraper supports a chain of n pages to get from the index pages to the actual images. This way it supports links like //Index Page->​Month Links->​Day Pages->​Images on day Page// The scraper supports a chain of n pages to get from the index pages to the actual images. This way it supports links like //Index Page->​Month Links->​Day Pages->​Images on day Page//
  
-The optional //!// in front of a regex tells the scraper to reverse the matches. This is helpful if the index page lists newest first.+The optional //!// in front of a regex tells the scraper to reverse the matches. This is helpful if the index page lists newest first. Alternatively you can specify the attribute **Reverse** to the part element. You can also sort the matches based on the text by specifying the **Sort** attribute.
  
 As with the BrowserScraper you can also omit the PageLinkType and simply start the Url with an //!// or put the regex expressions into a part list. As with the BrowserScraper you can also omit the PageLinkType and simply start the Url with an //!// or put the regex expressions into a part list.

Navigation