Quote:
Originally Posted by hpotter
The current storage (in .opf file) is the following:
meta name="calibre:user_metadata:#koboreadpct" content=" abcdef "
meta name="calibre:user_metadata:#kobolastread" content=" abcdef "
meta name="calibre:user_metadata:#koboreadloc" content=" abcdef "
Would it run with the following one (name being the MAC address)?
meta name="00:90:A2:xx:yy:zz" content="calibre:user_metadata:#koboreadpct = abcdef "
meta name="00:90:A2:xx:yy:zz" content="calibre:user_metadata:#kobolastread = abcdef "
meta name="00:90:A2:xx:yy:zz" content="calibre:user_metadata:#koboreadloc = abcdef "
It is just a question; I've no knowledge at all on the topic.
|
It isn't the data storage that I am working out, that will be the same as now. Except there will be a set of custom columns for each device. As to the content of the OPF, I have no control over that. Calibre writes that whenever it writes the metadata to the OPF file in the library or to the books. And the format of each attribute is defined. To use the MAC address, it would be part of the column name.
The issue is how to create that configuration. How to display on the screen and then store it in the configuration file. At the moment, I'm planning to use a similar method to the Reading List plugin. A tab for "Profiles" which have the device specific configuration, a tab for the list of known devices and a tab for all the other options (keyboard and the button configuration). You will be able to create as many profiles as you want. Each can be assigned to one device. Or one can be set for all unknown devices. This is effectively what happens now.
That feels like it will work. And it has the added advantage of being able to "borrow" a lot of code from