|
It's on my TODO list, but I have other priorities at the moment. Feel free to hack on it. Integrating monocle into the CS should be fairly trivial.
The hard part is writing a new iterator class that the ebook viewer and the content server can share, that caches the exploded ebooks files and supports concurrent access, annotations, etc.
But to start with you can just use the current oeb.iterator to enable basic read access with no caching. I can always re-write it to use the new iterator when the new iterator is ready.
Ask if you need guidance around the CS code.
|