home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
Improvement Suggestions
coming attractions page
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Anonymous" data-source="post: 4300"><p>Viewing by theatre or by movie has nothing to do with the scraper. The scraper simply populates the MovieData object. The movie object will allow data to be retrieved(movies in a theater or theaters for a movie). </p><p>I only implemented the theatre view, but all it would take is more code in the display part, not in the scrapping. </p><p></p><p>As far as a plugin architecture goes, it's almost there. Each scrapper defines it's supported countries. So when Germany is selected, it could iterate through the scrappers until it finds one that supports Germany. Then the scrapper can do it's job. It doesn't matter where it gets the information from, yahoo or anywhere else. That's abstracted from the rest of the plugin.</p><p>So the existing YahooScraper object can be renamed AmericasScraper maybe. </p><p></p><p>As far as a trailer viewer goes, I think, IMHO, that should be seperated from the scrapers. There could be one other class or set of classes that gets movie data from apple trailers for example, that's not country specific at all. Just like IMDB. The cast, plot etc for all movies scrapped from all countries can all come from IMDB. </p><p></p><p>If you guys like, I can set up this architecture fairly quickly. But I have one key request. This package will become a seperate project that will just be used by mediaportal. This way it can be reused for other applications. </p><p>I find it to be such a waste when somebody puts in a lot of effort in something like this, and they tailor it to one specific application. </p><p>I cringe when I think of how many IMDB scrapers there are out there all doing the exact same thing in the same programming languages. All that wasted effort!</p><p></p><p>Man. This should just turn into XMLMovie. Kind of like XMLTV. I smell a new sourceforge project. </p><p></p><p> <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /></p></blockquote><p></p>
[QUOTE="Anonymous, post: 4300"] Viewing by theatre or by movie has nothing to do with the scraper. The scraper simply populates the MovieData object. The movie object will allow data to be retrieved(movies in a theater or theaters for a movie). I only implemented the theatre view, but all it would take is more code in the display part, not in the scrapping. As far as a plugin architecture goes, it's almost there. Each scrapper defines it's supported countries. So when Germany is selected, it could iterate through the scrappers until it finds one that supports Germany. Then the scrapper can do it's job. It doesn't matter where it gets the information from, yahoo or anywhere else. That's abstracted from the rest of the plugin. So the existing YahooScraper object can be renamed AmericasScraper maybe. As far as a trailer viewer goes, I think, IMHO, that should be seperated from the scrapers. There could be one other class or set of classes that gets movie data from apple trailers for example, that's not country specific at all. Just like IMDB. The cast, plot etc for all movies scrapped from all countries can all come from IMDB. If you guys like, I can set up this architecture fairly quickly. But I have one key request. This package will become a seperate project that will just be used by mediaportal. This way it can be reused for other applications. I find it to be such a waste when somebody puts in a lot of effort in something like this, and they tailor it to one specific application. I cringe when I think of how many IMDB scrapers there are out there all doing the exact same thing in the same programming languages. All that wasted effort! Man. This should just turn into XMLMovie. Kind of like XMLTV. I smell a new sourceforge project. :D [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
Improvement Suggestions
coming attractions page
Contact us
RSS
Top
Bottom