View Single Post
Old 01-06-2012, 12:47 AM   #3
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: 6,283
Karma: 3966249
Join Date: Dec 2011
Location: Midwest USA
Device: Kindle Paperwhite(10th)
FanFictionDownLoader 1.1.0

Posting FanFictionDownLoader plugin 1.1.0, hoping to get some beta testers before pushing it out.

Internally, 1.1 is an almost complete re-write of the plugin from 1.0.

I was advised by more experienced plugin developers that the way I was handling background processing was not particularly safe. Given the number of unexpected crashes I kept getting working with 1.0, I saw their point.

1.1 uses Calibre's mechanism to launch separate background processes to download stories rather than using a background thread.

There is now a drop down menu from the plugin tool bar button for Add/Update/Configure/About.

Also, 'update' truly updates the book(s) selected now. Before the plugin gathered URLs from the selected books, but after that treated the URL as if the user had entered it. If the name or author on the book had been changed, either in Calibre or on the website, it would not update the existing book in Calibre, but treat it as a different book.

The plugin now downloads the stories, but does *not* add/update them in your library until all are downloaded and you confirm you want the updates. Again, this is because background processing updating the foreground is dangerous in Calibre.

There is (hopefully) better download error/update reporting now, but it could still use some more work.

There are more options now for how to update existing stories, whether by directly updating or by doing 'Add New' with a URL to a story that already exists in your library.

Under "Add New from URL(s)", there's an option to choose handling for "If Story Already Exists?". This is also sometimes called collision handling.

"Skip" and "Add New Book" should be self-explanatory.

"Update EPUB if New Chapters" and "Update EPUB Always" allow you to incrementally update a story you already have, but only if you use EPUB. "Update EPUB Always" will update the title page and metadata for the story even if there are no new chapters.

"Overwrite Always" will download the story and overwrite the chosen format. "Overwrite if Newer", only if the website story is newer.

"Update Calibre Metadata Only" does not download the story, only enough metadata to update the metadata Calibre keeps.

Update Existing's "Update Mode" is identical.

Under Configuration, there are some changes and new options.

With the split between "Add New" and "Update Existing", the options to take URLs from selected and prioritize selected vs clipboard are removed. There's still an option to take URLs from clipboard or not.

You can also make the menubar button always bring up "Add New" by unchecking "Default to Update when books selected?".

Jim

(Attachment removed after 1.1.1 posted.)

Last edited by JimmXinu; 01-08-2012 at 03:26 PM.
JimmXinu is offline