|
Interesting, thanks Ken! Maybe I'll try writing a plugin when I've got some spare time. I don't think the change would need to be reflected instantly, perhaps the next state change.
The approach I think I might implement would basically consist of a user configurable single external endpoint and on page-turn it would trigger an async POST within KOReader (with a device UID and maybe some useful statistics like current book title, progress stats etc if the users endpoint wanted to use it for something) and the endpoint could return a response with some JSON that would get validated by the plugin and change the appropriate setting
|