Thread: [Device Plugin] Kobo Touch Extended Driver
View Single Post
Old 04-21-2021, 03:26 AM   #2509
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 hpfr View Post
Awesome, you can't edit posts older than five minutes, so I had to retype that, and then the forum just decided to eat my post action, so third time's the charm, I guess? Maybe it's time to move to Discourse or something...
I think there is a minimum number of posts before you are allowed to edit your posts.
Quote:
I did find standalone.sh after digging around the installation guide's commit history, although baskerville has since removed mention of it, which is concerning.

I see now that Calibre's Device menu is missing the book I added while Plato was running, so I understand the database thing now. I guess Kobo Touch Extended can't modify the database while Plato is running, so I might as well use one of the plugins you mentioned which does similar folder actions as Kobo Touch Extended without the native Kobo database modifications?
The driver does not make changes to the database when sending new books (except in one case). It puts them on the device and when they device is disconnected, the device runs the import process and adds the books to the database. When you next connect the device, the driver will read the database and see those books.

If you put books on the device in such a way that the books are not imported into the database, then the driver will not see them. That could be done by using calibre to put the book on the device, but, going directly into Plato when you eject the device. Or, if Plato has a way to download a book, it will probably not be added to the database.

The driver will update the database for the following reasons:
  • Resending a book to replace it. The database gets updated in a way that the device will not treat it as a new book.
  • Metadata updates. The database is updated but the actual book is not.
  • Collection management.

The other work the KoboTouch and KoboTouchExtended drivers do is:
  • Generate and send covers.
  • Send kepubs.
  • Append some CSS to the stylesheets.

Very little of the above is useful if you do not use nickel. It is all about using a Kobo ereader as a Kobo ereader.

As I said, if you are not using nickel, you are probably better off not using either of the KoboTouch or KoboTouchExtended drivers. The other suggestions do disc scans looking for books and do not attempt to do anything more.
davidfor is offline   Reply With Quote