|
If it wasn't so much work, I'd slice each comic page into its individual tiles whenever possible. However that would increase the number of "pages" and Kobo isn't great at handling CBZ in the first place. One database entry per page when I last tried it.
Handling large graphics could be optimized (basically what's being done when you look at some gigapixel graphic sites, or Google maps, slice it into smaller units) but nobody will invest that kind of effort into a PDF/comic reader so most likely every time you zoom/scroll it will go back to square one and re-resize and re-crop the original big image and the CPU will struggle with that.
Long battery life is only if the device does nothing whatsoever which is the case when reading books, once the page is displayed [which in itself doesn't take much power for just text] it can twiddle its thumbs until the reader decides to flip the page which might be a long time later...
|