Quote:
Originally Posted by user_none
Just curious, are you not using the metadata caching code that I was using with the on device column? It included id's associated with the library entry so the file names didn't have to be modified?
|
No, not yet. Two reasons: 1) I am still looking at it to understand how it would work across all devices that support their own metadata, such as Sonys (as you know, non-trivial, but as I have one, important to me), and 2) am looking at a more general solution where the device isn't a 'device' but is instead an instance of a library. Option 2 is my preference, but Kovid says that if we go that way, he wants to redesign libraries from the ground up to have a plug-in architecture and support more-or-less arbitrary data sources - aka do a *lot* of work. He is willing to do the architecture work, and I am willing to try to implement some instances of it, so off we go. We will see...
Given the above, and because ondevice is such a useful thing to have, it seemed to make sense to slightly extend work you had already done to provide a more reliable indication. Adding the id to the name, which is what the Sonys already do, was the most straightforward and carried a minimal cost. Of course, it does not provide the performance enhancement that metadata caching gives, and it junks up the names a bit.