Quote:
Originally Posted by Terisa de morgan
Well, I have a question about relation between plugins. Would it be posible to call the Annotation plugins from other plugin (namely Kobo Utility). I usually lose notes because I don't remember to run the plugin after finishing the book before removing it. Before trying to analyze this plugin (as I've never checked the code), I wanted to ask davidfor's opinion about it (opinion, hands to develop it will be mine  )
|
Quote:
Originally Posted by Terisa de morgan
Or another option would be to start it automatically after connecting the device. I don't know, just not forgetting it 
|
I have thought of adding an automatic start, but there is one little problem with this. The annotations import requires one book to be selected. This is used with the Kindles and the other import methods as there the plugin does the matching between the books the annotations are for and the library. For Kindles, the annotations come from the clippings file. This has the title and author, but no direct reference to the book. The plugin does the matching to the library and can prompt to accept the match based on a confidence level for the match. If the plugin can't find a match, it suggests the selected book as the destination for the annotations. This was something the original author of the plugin did and I've never known if it was useful or not.
For the Kobo devices, the selected book won't be used. The plugin only fetches annotations for books that are already matched, and it uses this link to get the right book. Removing this for Kobo devices should be safe.
Calling the plugin from another plugin isn't hard. I call a function in the Goodreads sync from Kobo Utilities. Calling the annotations should be OK as well. But, an automatic fetch of the annotations is probably better. A problem with doing this is that the annotations fetch runs in the foreground. If it was a background job, it would be less intrusive especially when no annotations are found.