MobileRead Forums - View Single Post - [Device Plugin] Kobo Touch Extended Driver

jgoguen · 08-07-2013, 09:18 PM

If anyone is interested in testing out some new code, I'm looking for some guinea pigs kind and friendly people(1)

to try out the code on GitHub. There's a few things I'm interested in some intrepid testers taking a look at.

The Windows Powershell script to create the plugin ZIP files is untested and needs to be verified by someone running Windows with Powershell 2 or later installed. Sorry(2) Windows XP users, I think that may exclude you, but you can manually create the plugin ZIP files or download the attached ZIP files.
Some files were moved around to make it easier to separate this plugin from the conversion plugin and still share code. The KoboTouchExtended driver plugin should work exactly as before except for the missing options (next point).
Some driver options were removed (see some previous-but-recent post). The last option now should be the option to copy a generated KePub file to some directory and it should be a text field.
- The three database options at the end of the options list in the current version will be moved to the Kobo Utilities plugin, which is a much better home for them.
- The option to delete files not in the manifest became more trouble than I felt it was worth when I switched to the standard calibre OEB container implementation
In the formats list at the top of the KoboTouchExtended plugin preferences should include a 'kepub' entry (in alphabetical order, not selected by default). This only makes sense in the context of the new conversion output plugin, detailed later.

As you probably figured out by now, there's also a new conversion output format plugin to try out.
WARNING: THE CONVERSION OUTPUT FORMAT PLUGIN GENERATES FILES WHOSE INTERNAL STRUCTURE IS STILL UNDER DEVELOPMENT. THE KEPUB FILE STRUCTURE IS NOT YET FULLY UNDERSTOOD. DO NOT, UNDER ANY CIRCUMSTANCES, DELETE THE FILES FOR THE SOURCE FORMAT. ALWAYS HAVE A NON-KEPUB FORMAT FOR YOUR BOOKS.

The 'create-plugin' scripts should create the ZIP files for both plugins.
When you choose to convert a book, you can now choose 'KEPUB' from the output format list (top-right of the conversion window) and convert your books to Kobo's KePub format directly.
- Please don't delete the non-KePub formats for any books you convert. Just trust me, humour me even, and please don't do it. No matter how many times someone tells you it'll be fine. Especially not if you find yourself or someone else saying "what's the worst that could possibly happen" or "nothing could possibly go wrong"
If you convert a book to KePub and then send the book to the device, the upload process should be much faster as the driver skips the entire conversion pipeline for books in the 'kepub' format.
I haven't tried converting from any source format other than ePub, but as this leverages calibre's conversion routines it should Just Work for any supported input format.
- The list of input formats, in order of calibre's preference, is: LIT, MOBI, AZW, EPUB, AZW3, FB2, DOCX, HTML, PRC, ODT, RTF, PDB, TXT, PDF

Because calibre works with single extensions only, the files generated by the conversion output plugin have the extension 'kepub'. This shouldn't cause any problems when uploading to Kobo devices.

You'll notice that there's no conversion input format plugin. This is deliberate, and shouldn't cause any issues whatsoever because you're definitely going to heed my warning and always going to have a non-KePub format for your book. Right?

As part of this, the location of reference.kepub.epub has changed. Previously, it went in the KoboTouchExtended folder inside calibre's plugins folder, now it goes directly in calibre's plugins folder. Nothing uses the KoboTouchExtended folder anymore and it can be safely removed after updating to plugin version 2.1.1.

Any bugs can be reported in the usual way. The README file on GitHub (but not the copy in the first post) has been updated to be current for the new code, anything wrong or missing in the README should be considered a bug and reported accordingly.

(1) Not so kind and/or friendly people are also welcome. I'm an equal-opportunity tester seeker.

(2) Honestly, about 95% sorry that you're running Windows XP. You're a couple months away from running a 12 year old OS

08-07-2013, 09:18 PM	#588
jgoguen Generally Awesome Person Posts: 1,100 Karma: 2191133 Join Date: Jan 2013 Location: /dev/kmem Device: Kobo Clara HD, Kindle Oasis	If anyone is interested in testing out some new code, I'm looking for some guinea pigs kind and friendly people(1) to try out the code on GitHub. There's a few things I'm interested in some intrepid testers taking a look at. The Windows Powershell script to create the plugin ZIP files is untested and needs to be verified by someone running Windows with Powershell 2 or later installed. Sorry(2) Windows XP users, I think that may exclude you, but you can manually create the plugin ZIP files or download the attached ZIP files. Some files were moved around to make it easier to separate this plugin from the conversion plugin and still share code. The KoboTouchExtended driver plugin should work exactly as before except for the missing options (next point). Some driver options were removed (see some previous-but-recent post). The last option now should be the option to copy a generated KePub file to some directory and it should be a text field. The three database options at the end of the options list in the current version will be moved to the Kobo Utilities plugin, which is a much better home for them. The option to delete files not in the manifest became more trouble than I felt it was worth when I switched to the standard calibre OEB container implementation In the formats list at the top of the KoboTouchExtended plugin preferences should include a 'kepub' entry (in alphabetical order, not selected by default). This only makes sense in the context of the new conversion output plugin, detailed later. As you probably figured out by now, there's also a new conversion output format plugin to try out. WARNING: THE CONVERSION OUTPUT FORMAT PLUGIN GENERATES FILES WHOSE INTERNAL STRUCTURE IS STILL UNDER DEVELOPMENT. THE KEPUB FILE STRUCTURE IS NOT YET FULLY UNDERSTOOD. DO NOT, UNDER ANY CIRCUMSTANCES, DELETE THE FILES FOR THE SOURCE FORMAT. ALWAYS HAVE A NON-KEPUB FORMAT FOR YOUR BOOKS. The 'create-plugin' scripts should create the ZIP files for both plugins. When you choose to convert a book, you can now choose 'KEPUB' from the output format list (top-right of the conversion window) and convert your books to Kobo's KePub format directly. Please don't delete the non-KePub formats for any books you convert. Just trust me, humour me even, and please don't do it. No matter how many times someone tells you it'll be fine. Especially not if you find yourself or someone else saying "what's the worst that could possibly happen" or "nothing could possibly go wrong" If you convert a book to KePub and then send the book to the device, the upload process should be much faster as the driver skips the entire conversion pipeline for books in the 'kepub' format. I haven't tried converting from any source format other than ePub, but as this leverages calibre's conversion routines it should Just Work for any supported input format. The list of input formats, in order of calibre's preference, is: LIT, MOBI, AZW, EPUB, AZW3, FB2, DOCX, HTML, PRC, ODT, RTF, PDB, TXT, PDF Because calibre works with single extensions only, the files generated by the conversion output plugin have the extension 'kepub'. This shouldn't cause any problems when uploading to Kobo devices. You'll notice that there's no conversion input format plugin. This is deliberate, and shouldn't cause any issues whatsoever because you're definitely going to heed my warning and always going to have a non-KePub format for your book. Right? As part of this, the location of reference.kepub.epub has changed. Previously, it went in the KoboTouchExtended folder inside calibre's plugins folder, now it goes directly in calibre's plugins folder. Nothing uses the KoboTouchExtended folder anymore and it can be safely removed after updating to plugin version 2.1.1. Any bugs can be reported in the usual way. The README file on GitHub (but not the copy in the first post) has been updated to be current for the new code, anything wrong or missing in the README should be considered a bug and reported accordingly. (1) Not so kind and/or friendly people are also welcome. I'm an equal-opportunity tester seeker. (2) Honestly, about 95% sorry that you're running Windows XP. You're a couple months away from running a 12 year old OS Last edited by jgoguen; 08-08-2013 at 04:45 PM.