Quote:
Originally Posted by ibu
@Agama
My suggestion is pragmatically.
It would be may be to much pre parsing, if every target page of a link is pre parsed.
The target page for the first link is OK, I think. And in the typical case of endnotes, the target page will contain more than only the content of the first link, but also the second or third.
Usability studies always show: delay is evil. People don't like it (if they ever experienced a faster way)
|
I really think it's a non-starter and not at all pragmatic. (Pragmatic = "of or pertaining to a practical point of view or practical considerations." -
http://dictionary.reference.com/browse/pragmatic)
It would be a complete waste of time/battery to cache the first link if the user is interested in the 2nd, 3rd, Nth and not interested in the 1st. There's no way of telling what would be best to cache until the user clicks a link, and then - it's too late to bother caching!
We can expect eBook readers to continue to increase in performance and therefore make any pre-caching of flows unecessary. Until then either keep your end notes in the same flow as the text being noted, or make your end note flow suitably small so that it is quick to parse, (but bear in mind that a huge number of files referenced in the OPF will slow down book processing! See
https://www.mobileread.com/forums/sho...d.php?t=212892)
Caching ahead would also be likey to use up the battery more quickly, which would be most annoying.