Thread: [GUI Plugin] Library Codes
View Single Post
Old 10-13-2018, 10:17 PM   #132
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by DaltonST View Post
My response would sound like to someone who knew nothing about the Library Codes plugin, and knew nothing about the heavily modified Classify API (that was the topic of discussion in the first place) that it uses to obtain many of them.

The Library Codes plugin is 3 years old, and has been generating LCEAD Tags (Tag-Like Custom Column Tags) flawlessly for 3 years. FAST Tags are just a new source for a Tag-Like Custom Column. No big deal.

LC is a generic plug-in, and I will not hardcode anything special in its API for a single user. Calibre is powerful enough in functionality so a user can use standard Calibre functionality to achieve whatever they want without asking me to hardcode it just for them.

Since I have developed 14 plug-ins, I should be presumed a priori to know a little about programming plug-ins, using both Calibre's APIs and native SQLite, to create Tags in all of their flavors.
Firstly, I have already apologised for misunderstanding something you said. And in the above quoted section I was simply trying to explain that. And for the record, I have made no claims about your ability to code or your understanding of calibre. Except one, which I was attempting to apologise for.

One thing I was trying to understand in the second post was whether not changing the tags to allow them to be treated as a hierarchy was a technical issue (can't be done easily), or a philosophical decision (doesn't fit into the way you see the plugin or the tags should be used untouched). I can see that it is that latter.

It definitely isn't a technical issue as it took me about five minutes to find the line to change to do this. For the record, all that is needed is to change line 704 in ui.py from:

Code:
fast_list = fast_dict[s_book]
to:

Code:
fast_list = [tag.replace("--", ".") for tag in fast_dict[s_book]]
Of course, it would be better if it was configurable. So, what do you think? 30 minutes to add a checkbox, store the preference and check it when doing the above?
davidfor is offline   Reply With Quote