It serves as identification between browser and server. Technically necessary for the basic operation of the system.īased on the session cookie, our shop decides whether the respective user has an active shopping cart and whether the user is logged in. The website can not run faultless without these cookies. When there are extra libraries needed, you need to package them into the jar file using the maven shade plugin.These necessary cookies are by any means required for the running of the website and allow for example system- and safety relevant functions, functions of a shopping cart and the basic storing of the allowed cookie settings. For a detailed list of used libraries please refer to the pom.xml of the tinyMediaManager project. The meta data will be included in the MediaProviderInfo of the protected MediaProviderInfo createMediaProviderInfo () Available libs/toolsĪ creator of a third party library can use all libraries which tinyMediaManager uses itself. Configuration parameters (for fine tuning your scraper - e.g.Logo (will be described in the settings and scraper drop downs). Description (will be displayed in the settings).the movie meta data area needs other settings than the movie artwork area) Scraper Sub-Id (especially interesting if you want to differentiate settings in the areas of the scraper.Scraper Id (do not re-use this id across different scrapers!).This meta data is displayed in tinyMediaManager itself (scraper selection, settings, …) and consist of: If you create an own scraper, you need some meta data for the scraper in addition to the pure code. ITvShowSubtitleProvider - the class offers scraping of subtitles for TV shows (example: SampleTvShowSubtitleProvider.java).ITvShowTrailerProvider - the class offers scraping of trailers for TV shows (example: SampleTvShowTrailerProvider.java).ITvShowArtworkProvider - the class offers scraping of artwork for TV shows (example: SampleTvShowArtworkProvider.java).ITvShowMetadataProvider - the class offers scraping of meta data for TV shows (example: SampleTvShowMetadataProvider.java).IMovieSubtitleProvider - the class offers scraping of subtitles for movies (example: SampleMovieSubtitleProvider.java) IMovieTrailerProvider - the class offers scraping of trailers for movies (example: SampleMovieTrailerProvider.java).IMovieArtworkProvider - the class offers scraping of artwork for movies (example: SampleMovieArtworkProvider.java).IMovieMetadataProvider - the class offers scraping of meta data for movies (example: SampleMovieMetadataProvider.java).if the scraper just provides meta data for TV shows only the interface ITvShowMetadataProvider needs to be implemented. The third party scraper just needs to implement the interfaces where data can be provided. In our example this file just needs one entry: .SampleAddonProvider. To enable the Java Service Provider (SPI) you also need to create a file called META-INF/services/.IAddonProvider containing the path to the loader class. The scraper classes itself need to implement the corresponding interfaces to tell tinyMediaManager which scraper functionalities are provided. The Method getAddonClasses will offer tinyMediaManager a list of classes which offer scraper functions. SampleAddonProvider.java - this class is the main connector between the custom scraper and tinyMediaManager itself.This repository has one special class and some other examples. To create a custom scraper you can use (fork or clone) the template repository which already offers the right structure for a custom scraper. After the next restart, tinyMediaManager will be able to use this scraper the same way as internal scrapers. jar file and put it into the subfolder addons of the tinyMediaManager installation. The user just needs to download the generated. Using this interface any developer can create a scraper and publish it. TinyMediaManager’s next release (v4.2) will introduce an interface for third party scrapers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |