2007-01-18, 23:39
1) the db is there for speed. having it remote would negate this.
2) the sqlite code is a self contained library and doesnt know anything about xbmc's "filesystems". thus the db has to be local. while it could be changed to be made aware of xbmc's filesystems, see #1.
and personally, i dont think there should be dependancy on library view from files view. its files view. if yuo want the enhanced info, use the library. tahts why its there.
but i did add a way to allow finding info in "remote" imdb xml files. its basically the same imdb xml file on a remote share. the "manual add to database" function looks for these files based on filename. i'm not saying it will be done, but it is concievable to load that info if found.
** edit **
i see you have "listitem.tagline" above. this is not part of the information which is accessible from a list, but is only available in the info window. the difference being that the information which is available to the lists is in the database. all the other stuff is loaded out of a cached xml file.
2) the sqlite code is a self contained library and doesnt know anything about xbmc's "filesystems". thus the db has to be local. while it could be changed to be made aware of xbmc's filesystems, see #1.
and personally, i dont think there should be dependancy on library view from files view. its files view. if yuo want the enhanced info, use the library. tahts why its there.
but i did add a way to allow finding info in "remote" imdb xml files. its basically the same imdb xml file on a remote share. the "manual add to database" function looks for these files based on filename. i'm not saying it will be done, but it is concievable to load that info if found.
** edit **
i see you have "listitem.tagline" above. this is not part of the information which is accessible from a list, but is only available in the info window. the difference being that the information which is available to the lists is in the database. all the other stuff is loaded out of a cached xml file.