Thread: Library names
View Single Post
Old 02-28-2011, 12:54 PM   #39
kiwidude
Calibre Plugins Developer
kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.
 
Posts: 4,732
Karma: 2197770
Join Date: Oct 2010
Location: Australia
Device: Kindle Oasis
Quote:
Originally Posted by kovidgoyal View Post
I think what kiwidude is asking for is a centrally maintained cache of seen uuid-name mappings that are automatically updated by the device subsystem on connect of a device.
Exactly. I don't have an issue with the name being stored on a device - the plus being as you say it can default when you plug into a new Calibre instance, the minus being you have to handle the issue of renaming/duplication if stored elsewhere.

But each plugin building up a device id/name map as it goes seems like some duplication that could be avoided if Calibre was to store a dictionary of UUID/name in prefs of devices it has "seen". The GUI around that would allow you to rename for a device (to cater for chaley's "my son" example), remove devices no longer used etc.

Then each plugin could just query that dictionary to present options/menus for a user related to that device.
kiwidude is offline   Reply With Quote