View Single Post
Old 08-19-2013, 06:39 AM   #1611
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 JimmXinu View Post
There's a link to the project home page in the first post. I'm open to accepting code contributions and to giving regular contributors write perms to the source repository.
I had a suspicion that would be the answer We'll see how annoyed I get by it.
Quote:
Before the plugin version, when I first re-wrote FFDL, it did exactly that. However, I couldn't find a way to dynamically find and load the files from the plugin zip within calibre. So when the plugin version came along, that went away.

It's been a couple years since then and I haven't looked at the Annotations plugin. But dynamically loading files would only improve the development loop if it also detected and reloaded updated files. And the number of users who would benefit from it can be counted on one hand, I expect. (I use the CLI when developing new adapters, which side steps the problem neatly.)
I had a look at the Annotations plugin a while ago to add support for the Kobo devices. It loads classes for the devices from both the zip file and a configurable directory. But, you're right, it wouldn't be used by many people. The CLI is probably the way to go the next time I'm playing.

Quote:
I have been toying with the idea of adding some sort of user-added code system to allow python code to be entered similar to personal.ini and then called at different points in FFDL's execution to change the story. Pre/post processors for chapter text, metadata, etc. Up to now, however, none of the users wanting the most specific levels of control have had any python skills.
User exists are always nice, but a pain for the support person.
Quote:

It continues to amaze me how much effort people will put into massaging their metadata. By contrast, except for usernames/passwords, this is the entirety of my personal.ini:
Code:
# Library
.
.
.
replace_metadata:
 author=>Bobmin356=>Bobmin
Short and sweet. I suspect that mine will get complicated and then in six months I'll look at it and wonder why it has all that rubbish.
davidfor is offline