Thread: "Fetch annotations (experimental)" person/group
View Single Post
Old 09-10-2014, 10:43 PM   #2
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
I'm not responsible for the fetch annotations function, but have done some work on it and related things.

The function is there and works. But, it needs code in the driver of each device to work. The KoboTouch driver has it and at least one other has it. I think the Kindle, but I'm not sure. It works, but I have never been a fan of it. This is more of a "doesn't fit my needs" thing than any real problem with it.

As an alternative to this, there is the Annotations plugin. This does basically the same thing, but has some options including formatting the stored annotations and specifying where they go. Plus it updates them rather than replacing them. This was written by someone else, but I am the current maintainer. This also needs code for each device, but it can be easily added within the framework the plugin supplies. I'm happy if you want to do anything with this.
davidfor is offline   Reply With Quote