2008-08-28, 02:40
I am not sure if Jonathan (jmarshall) wants us to continue the discussion here about suggestions on how this could be implemented, so until then... 
Tell me if I am wrong but I suspect that in order to work, a ListItem implementation requires the "ListItem array of properties" to be loaded. I sense this is different from the fanart implementation which probably just follows a simple expression to construct the fanart filename (movie-fanart.jpg)...
Parsing an xml file maybe taking a little more time but we are talking about xml here so a fairly good structure like this could load in no time. Let me expand on that:
In comparison with the Enable Tag Reading from the audio section (which is read from binary files), I believe we wouldn't see a performance issue at all (unless there are hundreds of movies in one folder which would beat the purpose of using folders and not the video library). In order to read the audio tags, the whole file must first be "opened", i.e. several Mg per file... An xml file like this would at the MAX be 4k and would be parsed in ms, even on a VERY old xbox.
In term of supporting this, I don't think it requires a full setup file section on a per folder basis. I think kraqh3d's suggestions makes sense. What about just just adding a "Enable NFO file reading" option in Settings/Video/General/ or even a duplicate of the settings for audio tags (Settings/Video/Files/ with matching template filename expression) ?
I'll leave to the expert a way to deal with the database but something like the Audio tags for video seems the right way, less difficult, and faster to implement. (maybe before november ?...)
My 2 cents...
Jonathan, does it make sense?
Thanks
Tell me if I am wrong but I suspect that in order to work, a ListItem implementation requires the "ListItem array of properties" to be loaded. I sense this is different from the fanart implementation which probably just follows a simple expression to construct the fanart filename (movie-fanart.jpg)...
Parsing an xml file maybe taking a little more time but we are talking about xml here so a fairly good structure like this could load in no time. Let me expand on that:
In comparison with the Enable Tag Reading from the audio section (which is read from binary files), I believe we wouldn't see a performance issue at all (unless there are hundreds of movies in one folder which would beat the purpose of using folders and not the video library). In order to read the audio tags, the whole file must first be "opened", i.e. several Mg per file... An xml file like this would at the MAX be 4k and would be parsed in ms, even on a VERY old xbox.
In term of supporting this, I don't think it requires a full setup file section on a per folder basis. I think kraqh3d's suggestions makes sense. What about just just adding a "Enable NFO file reading" option in Settings/Video/General/ or even a duplicate of the settings for audio tags (Settings/Video/Files/ with matching template filename expression) ?
I'll leave to the expert a way to deal with the database but something like the Audio tags for video seems the right way, less difficult, and faster to implement. (maybe before november ?...)
My 2 cents...
Jonathan, does it make sense?
Thanks
