Quote:
Originally Posted by rfog
ePub is a bunch of some kind of HTML + CSS files, normally (but not always) separated by chapters (that is, one file, one chapter).
It seems they are reading and parsing each HTML file after passing the last page of the previous one. Other readers a) load the entire book or b) caches the previous and next html file.
|
Sure, I get that, but there are plenty of ePub eReaders out there that don't have long loading screens in between chapters, so it's not like this is an issue inherent to the design of ePubs.
I guess what I'm asking is if this is something the dev will address, since it looks bad and adds in a delay that is not present in other eReaders. This app has plenty of useful features to help make an eBook display however you want, and I'd love to use it (especially since I've paid for it already), but the delay and loading icon are unsightly and pretty much negate setting up a custom look for your eBooks.
It would also appear another user is asking about something similar with the long loading times of PDFs. It would seem the rendering engine for this app needs some serious work and it's not just ePubs that suffer. For how powerful our devices are, delay and visible loading icons is the last thing I expect when doing something as untaxing as using an eReader.