Quote:
|
It was originally about allowing users to easily maintain multiple lists of books in an order that they want to read them - that is where the "order" comes in. You can specify the order when you edit a list - there are up/down buttons on that screen allowing you to change it, and the results are reflected when you view the list.
|
And that really seemed important enough for a plugin? People were maintaining large lists of books they wanted to read, in order? Well, okay, I guess.
Quote:
|
As for the rest - you got it right when you said you don't understand the calibre API or the reasons why many plugins don't use custom columns. And having an attitude about it doesn't exactly engender me to try to explain it.
|
The Reading List plugin does use custom columns. It can set and remove tags from them just fine. It just doesn't read them.
Now, it's entirely possible there's some sort of problem
reading them that I don't know about. But it seems to be able to individually read information from books just fine, and I can pull up a reading list of over 250 books and it can instantly get the information about them. (I checked, it reflects metadata change after being added to the list.)
And I have other plugins that, when I click on a book, they alter what menu items they present based on the metadata (For example, Goodreads changes based on whether or not the book has the goodread metadata added.) so clearly there's not any sort of delay there, either.
But if you don't want to tell me the super-secret reason that plugins can't use the user-facing-and-editable 'toggles set on books' that are tags and custom columns, and instead have to use their own internal, no-user-or-other-plugin-can-alter-it toggles, I guess I can't force you.