Deployed 8ce9f05 with MkDocs version: 0.17.2

00_Prepare_everything/index.html

@@ -9,11 +9,11 @@
   
   <link rel="shortcut icon" href="../img/favicon.ico">
   <title>Prepare everything - NewPipe Tutorial</title>
-  <link href='https://fonts.googleapis.com/css?family=Lato:400,700|Roboto+Slab:400,700|Inconsolata:400,700' rel='stylesheet' type='text/css'>
+  <link rel="stylesheet" href="../css/local_fonts.css" type="text/css" />
 
   <link rel="stylesheet" href="../css/theme.css" type="text/css" />
   <link rel="stylesheet" href="../css/theme_extra.css" type="text/css" />
-  <link rel="stylesheet" href="../css/highlight.css">
+  <link rel="stylesheet" href="../css/highlight.css" type="text/css" />
   
   <script>
     // Current page data

01_Basic_concept_of_the_extractor/index.html

@@ -9,11 +9,11 @@
   
   <link rel="shortcut icon" href="../img/favicon.ico">
   <title>Basic Concept of the Extractor - NewPipe Tutorial</title>
-  <link href='https://fonts.googleapis.com/css?family=Lato:400,700|Roboto+Slab:400,700|Inconsolata:400,700' rel='stylesheet' type='text/css'>
+  <link rel="stylesheet" href="../css/local_fonts.css" type="text/css" />
 
   <link rel="stylesheet" href="../css/theme.css" type="text/css" />
   <link rel="stylesheet" href="../css/theme_extra.css" type="text/css" />
-  <link rel="stylesheet" href="../css/highlight.css">
+  <link rel="stylesheet" href="../css/highlight.css" type="text/css" />
   
   <script>
     // Current page data
@@ -109,21 +109,23 @@
                 <h1 id="basic-concept-of-the-extractor">Basic Concept of the Extractor</h1>
 <h2 id="collectorextractor-pattern">Collector/Extractor pattern</h2>
 <p>Before we can start coding our own service we need to understand the basic concept of the extractor. There is a pattern
-you will find all over the code. It is called to <strong>extractor/collector</strong> pattern. The idea behind this pattern is that
+you will find all over the code. It is called the <strong>extractor/collector</strong> pattern. The idea behind this pattern is that
 the <a href="https://teamnewpipe.github.io/NewPipeExtractor/javadoc/org/schabi/newpipe/extractor/Extractor.html">extractor</a>
 would produce single peaces of data, and the collector would take it and form usable data for the front end out of it.
 The collector also controls the parsing process, and takes care about error handling. So if the extractor fails at any
-point the collector will decide weather it should continue parsing or not. This requires the extractor to be made out of
+point the collector will decide whether it should continue parsing or not. This requires the extractor to be made out of
 many small methods. One method for every data field the collector wants to have. The collectors are provided by NewPipe.
 You need to take care of the extractors.</p>
 <h3 id="usage-in-the-front-end">Usage in the front end</h3>
 <p>So typical call for retrieving data from a website would look like this:</p>
 <pre><code class="java">Info info;
 try {
-    Extractor extractor = new Extractor(ome_meta_info);   // Create a new Extractor with a given context provided as parameter.
-    info = Info.getInfo(extractor);                       // Retrieves the data form extractor and builds info package.
+    // Create a new Extractor with a given context provided as parameter.
+    Extractor extractor = new Extractor(ome_meta_info);
+    // Retrieves the data form extractor and builds info package.
+    info = Info.getInfo(extractor);
 } catch(Exception e) {
-    // handler errors when collector decided to break up extraction
+    // handle errors when collector decided to break up extraction
 }
 </code></pre>
               

css/local_fonts.css

@@ -0,0 +1,60 @@
+/*
+  Stylesheet to load all local fonts except Font-Awesome because that is done by the theme.
+  Add all new fonts below.
+ */
+
+@font-face {
+  font-family: 'Inconsolata';
+  font-style: normal;
+  font-weight: 400;
+  src: local('Inconsolata'), local('Inconsolata-Regular'), url(../fonts/Inconsolata-Regular.ttf) format('truetype');
+}
+
+@font-face {
+  font-family: 'Inconsolata';
+  font-style: normal;
+  font-weight: 700;
+  src: local('Inconsolata Bold'), local('Inconsolata-Bold'), url(../fonts/Inconsolata-Bold.ttf) format('truetype');
+}
+
+@font-face {
+  font-family: 'Lato';
+  font-style: normal;
+  font-weight: 400;
+  src: local('Lato Regular'), local('Lato-Regular'), url(../fonts/Lato-Regular.ttf) format('truetype');
+}
+
+@font-face {
+  font-family: 'Lato';
+  font-style: normal;
+  font-weight: 700;
+  src: local('Lato Bold'), local('Lato-Bold'), url(../fonts/Lato-Bold.ttf) format('truetype');
+}
+
+@font-face {
+  font-family: 'Lato';
+  font-style: italic;
+  font-weight: 400;
+  src: local('Lato Italic'), local('Lato-Italic'), url(../fonts/Lato-Italic.ttf) format('truetype');
+}
+
+@font-face {
+  font-family: 'Lato';
+  font-style: italic;
+  font-weight: 700;
+  src: local('Lato Bold Italic'), local('Lato-BoldItalic'), url(../fonts/Lato-BoldItalic.ttf) format('truetype');
+}
+
+@font-face {
+  font-family: 'Roboto Slab';
+  font-style: normal;
+  font-weight: 400;
+  src: local('Roboto Slab Regular'), local('RobotoSlab-Regular'), url(../fonts/RobotoSlab-Regular.ttf) format('truetype');
+}
+
+@font-face {
+  font-family: 'Roboto Slab';
+  font-style: normal;
+  font-weight: 700;
+  src: local('Roboto Slab Bold'), local('RobotoSlab-Bold'), url(../fonts/RobotoSlab-Bold.ttf) format('truetype');
+}

index.html

@@ -9,11 +9,11 @@
   
   <link rel="shortcut icon" href="./img/favicon.ico">
   <title>Welcome to NewPipe Tutorial - NewPipe Tutorial</title>
-  <link href='https://fonts.googleapis.com/css?family=Lato:400,700|Roboto+Slab:400,700|Inconsolata:400,700' rel='stylesheet' type='text/css'>
+  <link rel="stylesheet" href="./css/local_fonts.css" type="text/css" />
 
   <link rel="stylesheet" href="./css/theme.css" type="text/css" />
   <link rel="stylesheet" href="./css/theme_extra.css" type="text/css" />
-  <link rel="stylesheet" href="./css/highlight.css">
+  <link rel="stylesheet" href="./css/highlight.css" type="text/css" />
   
   <script>
     // Current page data
@@ -161,5 +161,5 @@ This however is not the <a href="https://teamnewpipe.github.io/NewPipeExtractor/
 
 <!--
 MkDocs version : 0.17.2
-Build Date UTC : 2018-02-22 18:22:22
+Build Date UTC : 2018-02-23 20:18:58
 -->

search/search_index.json

@@ -42,7 +42,7 @@
         },
         {
             "location": "/01_Basic_concept_of_the_extractor/",
-            "text": "Basic Concept of the Extractor\n\n\nCollector/Extractor pattern\n\n\nBefore we can start coding our own service we need to understand the basic concept of the extractor. There is a pattern\nyou will find all over the code. It is called to \nextractor/collector\n pattern. The idea behind this pattern is that\nthe \nextractor\n\nwould produce single peaces of data, and the collector would take it and form usable data for the front end out of it.\nThe collector also controls the parsing process, and takes care about error handling. So if the extractor fails at any\npoint the collector will decide weather it should continue parsing or not. This requires the extractor to be made out of\nmany small methods. One method for every data field the collector wants to have. The collectors are provided by NewPipe.\nYou need to take care of the extractors.\n\n\nUsage in the front end\n\n\nSo typical call for retrieving data from a website would look like this:\n\n\nInfo info;\ntry {\n    Extractor extractor = new Extractor(ome_meta_info);   // Create a new Extractor with a given context provided as parameter.\n    info = Info.getInfo(extractor);                       // Retrieves the data form extractor and builds info package.\n} catch(Exception e) {\n    // handler errors when collector decided to break up extraction\n}",
+            "text": "Basic Concept of the Extractor\n\n\nCollector/Extractor pattern\n\n\nBefore we can start coding our own service we need to understand the basic concept of the extractor. There is a pattern\nyou will find all over the code. It is called the \nextractor/collector\n pattern. The idea behind this pattern is that\nthe \nextractor\n\nwould produce single peaces of data, and the collector would take it and form usable data for the front end out of it.\nThe collector also controls the parsing process, and takes care about error handling. So if the extractor fails at any\npoint the collector will decide whether it should continue parsing or not. This requires the extractor to be made out of\nmany small methods. One method for every data field the collector wants to have. The collectors are provided by NewPipe.\nYou need to take care of the extractors.\n\n\nUsage in the front end\n\n\nSo typical call for retrieving data from a website would look like this:\n\n\nInfo info;\ntry {\n    // Create a new Extractor with a given context provided as parameter.\n    Extractor extractor = new Extractor(ome_meta_info);\n    // Retrieves the data form extractor and builds info package.\n    info = Info.getInfo(extractor);\n} catch(Exception e) {\n    // handle errors when collector decided to break up extraction\n}",
             "title": "Basic Concept of the Extractor"
         },
         {
@@ -52,12 +52,12 @@
         },
         {
             "location": "/01_Basic_concept_of_the_extractor/#collectorextractor-pattern",
-            "text": "Before we can start coding our own service we need to understand the basic concept of the extractor. There is a pattern\nyou will find all over the code. It is called to  extractor/collector  pattern. The idea behind this pattern is that\nthe  extractor \nwould produce single peaces of data, and the collector would take it and form usable data for the front end out of it.\nThe collector also controls the parsing process, and takes care about error handling. So if the extractor fails at any\npoint the collector will decide weather it should continue parsing or not. This requires the extractor to be made out of\nmany small methods. One method for every data field the collector wants to have. The collectors are provided by NewPipe.\nYou need to take care of the extractors.",
+            "text": "Before we can start coding our own service we need to understand the basic concept of the extractor. There is a pattern\nyou will find all over the code. It is called the  extractor/collector  pattern. The idea behind this pattern is that\nthe  extractor \nwould produce single peaces of data, and the collector would take it and form usable data for the front end out of it.\nThe collector also controls the parsing process, and takes care about error handling. So if the extractor fails at any\npoint the collector will decide whether it should continue parsing or not. This requires the extractor to be made out of\nmany small methods. One method for every data field the collector wants to have. The collectors are provided by NewPipe.\nYou need to take care of the extractors.",
             "title": "Collector/Extractor pattern"
         },
         {
             "location": "/01_Basic_concept_of_the_extractor/#usage-in-the-front-end",
-            "text": "So typical call for retrieving data from a website would look like this:  Info info;\ntry {\n    Extractor extractor = new Extractor(ome_meta_info);   // Create a new Extractor with a given context provided as parameter.\n    info = Info.getInfo(extractor);                       // Retrieves the data form extractor and builds info package.\n} catch(Exception e) {\n    // handler errors when collector decided to break up extraction\n}",
+            "text": "So typical call for retrieving data from a website would look like this:  Info info;\ntry {\n    // Create a new Extractor with a given context provided as parameter.\n    Extractor extractor = new Extractor(ome_meta_info);\n    // Retrieves the data form extractor and builds info package.\n    info = Info.getInfo(extractor);\n} catch(Exception e) {\n    // handle errors when collector decided to break up extraction\n}",
             "title": "Usage in the front end"
         }
     ]

sitemap.xml

@@ -4,7 +4,7 @@
     
     <url>
      <loc>/</loc>
-     <lastmod>2018-02-22</lastmod>
+     <lastmod>2018-02-23</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -12,7 +12,7 @@
     
     <url>
      <loc>/00_Prepare_everything/</loc>
-     <lastmod>2018-02-22</lastmod>
+     <lastmod>2018-02-23</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -20,7 +20,7 @@
     
     <url>
      <loc>/01_Basic_concept_of_the_extractor/</loc>
-     <lastmod>2018-02-22</lastmod>
+     <lastmod>2018-02-23</lastmod>
      <changefreq>daily</changefreq>
     </url>