diff --git a/01_Concept_of_the_extractor/index.html b/01_Concept_of_the_extractor/index.html index 11333bf..ed98f23 100644 --- a/01_Concept_of_the_extractor/index.html +++ b/01_Concept_of_the_extractor/index.html @@ -159,14 +159,14 @@ try {

Collector/Extractor pattern for lists

Sometimes information can not be represented as a structure, but as a list. In NewPipe an item of a list is called InfoItem. In order -to get such items a InfoItemsCollector -is used. For each item that should be extracted a new Extractor will be given to the InfoItemCollector via commit().

+to get such items a InfoItemsCollector +is used. For each item that should be extracted a new Extractor will be given to the InfoItemCollector via commit().

InfoItemsCollector_objectdiagram.svg

When a streaming site shows a list it usually offers some additional information about that list, like it's title, a thumbnail or its creator. Such info can be called list header.

Also if you open a list in a web browser the website usually does not load the whole list, but only a part of it. In order to get more you may have to click on a next page button, or scroll down. This is why a list in -NewPipe is coped down into InfoItemPages. Each Page has its own URL, and needs to be extracted separately.

+NewPipe is coped down into InfoItemPages. Each Page has its own URL, and needs to be extracted separately.

List header information and extracting multiple pages of an InfoItem list can be handled by a ListExtractor

diff --git a/index.html b/index.html index 6e742a5..d42be7c 100644 --- a/index.html +++ b/index.html @@ -161,5 +161,5 @@ This however is not the