2012-07-01, 04:57
(2012-06-27, 12:59)DonJ Wrote:(2012-06-16, 11:30)topfs2 Wrote: I'm not 100% I follow, I'd love some more examples. What I'm not sure is if you want the cnfiguration as an xbmc user or as xbmc (code using this engine) or as a scraper developer? I haven't 100% decided what will trigger the scanning, what I'm focusing on mostly now is when you know file X exist and want to gather data on it what to do. I'd love some thoughts on the actual scanning process too if its of interest in this project.
I think the file scanning process should be completely decoupled from the scraping process. Hence the process would be as follows:
1) "Something" finds a file (this something might be an addon, it might be an external tool which notifies xbmc via e.g. JSON or it might be the integrated xbmc file scanner)
2) The path to the file or directory is pushed to the scraper which starts the process to gather meta data via xml scrapers etc.
Therefore, the important part imo is to create a good/easy to use api to push paths/directories to the scraper. The same api should probably also allow the deletion of data from the library.
I think this would really open up the file scanning process to third party addon/tool developers. Hope this helps at all.
on a similar note, it should be possible to push ids (imdib, tmdbid, tvdbid and such) to the scrapers in a way that it can be called from the json-rpc interface that's under development.
