Thread: [Device Plugin] Kobo Touch Extended Driver
View Single Post
Old 10-09-2017, 07:19 PM   #1753
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 JSWolf View Post
But, putting metadata updating into the Reading List plugin would benefit more than Kobo users.
No it wouldn't. If you look, all the other devices either update the metadata automatically when the device is connected, or don't update it at all. As far as I know, Kobo Utilities is the only way to update metadata on the device that isn't in the driver. So to have the Reading List plugin update the metadata for any device, someone would need to add code to the plugin to be able to update the metadata for all the devices out there. And, that would be very time consuming. And to be honest way beyond stupid.

The sensible way is to use the Reading List plugin as a way to collect books. Other plugins can then be configured to use a list as an input to do some action. Such as the Kobo Utilities using a list as the set of books to update the metadata for on the device.

Now the Reading List plugin can trigger uploading books when a device is connected. So, it could be possible to add function to call another plugin when the device is connected and supply the list as a input. That is a good idea, with only one issue.

The issue? There is only one plugin out there that has function that makes sense to be called when a device is plugged in. Can you guess which it is? Yes, Kobo Utilities plugin.*

There are other issues, but, they are design/development ones. Such as, do you allow multiple plugins to be called? If so, what order? What if one fails? And we starting jobs or waiting for function to finish before the next.

* Well not quite true, but I'll let you work out why. And please, actually look at the plugins before you use them for justification.
davidfor is offline   Reply With Quote