Quote:
Originally Posted by davidfor
That's a good trick. But, it means for every column that you need to do this for, you need a second indicator column. Plus the extra non-display text is going to make the database a bit bigger.
|
The extra text could be a problem, the columns... not so much as they already need them for my jacket
Quote:
Originally Posted by davidfor
Today, I've been looking at the metadata plugboard. Calling that to do the substitution turned out to be simple. But, the template is probably no simpler. To do what I did last night, I have:
Code:
{comments}{tags:|<p>Tags: |</p>}{rating:|<p>Rating: |</p>}{#kobo_last_read:|<p>Last Read: |</p>}{#words:|<p>Word count: |</p>}
That produces what I thinking about. But, I'm not sure if it is better than the other template. I think the first version is simpler to create. This version a lot more flexible. |
Not so complicated, really.
Quote:
Originally Posted by davidfor
My thoughts on this metadata update function in the utilities plugin are:
- Decide on the template. Or prevaricate and somehow support both.
- Add an option to not to update downloaded kepubs. I should have done this ages ago.
- Read the template from the root of the device. If there isn't one there, look in the resources directory of the calibre configuration directory. This allows different configuration for different devices. And that would be handy for people who share a calibre installation.
- Maybe put the updates into a job. If I do this, I would consider adding an option to run this automatically on connect.
|
The template at the device could be handy, and the last option would be the same, for me, that adding it to the driver.
Quote:
Originally Posted by davidfor
Once I have this out, I'll start looking at the driver again It should be updating the metadata at the same time as the series info. Part of why I haven't done it is performance. No matter how I do it, it's going to add some time to the initial connection jobs. Adding the comments template might be a bit trickier as the driver code is separate from the Utilities plugin. But, I'll think about it.
|
As I said, I was being greedy, nothing else.