View Single Post
Old 08-18-2013, 11:48 PM   #1610
JimmXinu
Plugin Developer
JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.
 
JimmXinu's Avatar
 
Posts: 7,012
Karma: 4604635
Join Date: Dec 2011
Location: Midwest USA
Device: Kobo Clara Colour running KOReader
Quote:
Originally Posted by davidfor View Post
Ugly, but that should work for what I want. I have only seen a couple that I wanted to do this wit, o it won't be a problem. Of course, the programmer in me says to find the code and change it
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.

Quote:
Originally Posted by davidfor View Post
On a separate note, have you considered dynamically loading the adapters from a directory? ...
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 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.

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:
Spoiler:
Code:
# Library

[defaults]
is_adult: true

include_subject_tags: extratags, genre, category, status

strip_chapter_numbers:true
add_chapter_numbers:true

[epub]
include_tocpage: false
include_titlepage: true
include_logpage: smart
logpage_entries: fulldownload,dateCreated,datePublished,dateUpdated,numChapters,numWords,status,version,title,storyUrl,series,author,category,genre,rating,warnings,description

include_images:true
keep_summary_html:true
make_firstimage_cover:true

# so overwrite downloads have some marker.  
add_to_extra_valid_entries:,fulldownload
include_in_fulldownload:title
fulldownload_label:New Download

add_to_replace_metadata:
 fulldownload=>^.*$=>Yes

add_to_generate_cover_settings:
 ${anthology}=>true=>FFDL

[www.fanfiction.net]
never_make_cover: true
replace_metadata:
 author=>Bobmin356=>Bobmin
JimmXinu is offline