View Single Post
Old 04-02-2013, 02:47 PM   #36
Junior Member
daffy began at the beginning.
Posts: 11
Karma: 10
Join Date: Mar 2013
Device: Kindle PW
Originally Posted by knc1 View Post
And how can that target location be identified in the file?
Many of these formats do not have "hard" page breaks.
Without wishing to extend any support for this request, I might have an interpretation that would be workable with HTML:

Imagine a HTML file rendered to a virtual canvas featuring exactly the same width as the device's physical width. Then paginate the virtual canvas height by the device height. Voilá - paging

(The implementation would probably consume heaps of memory and CPU, not good).

Alternatively, allow for relative navigation in HTML, e.g. "plain" page down, "faster" page down (== 3x plain page down), "fastest" page down (== 9x plain page down) with exponential scrolling behaviour. This allows for faster navigation in what is inherently a single linear representation. For that to work, it wouldn't even be necessary to render to the output device. Rendering to a bitmap and blipping that in (in case the Kindle graphics stack supports that) would be sufficient, so this could be memory conservative.

Again, not supporting the feature request, just airing ideas
daffy is offline   Reply With Quote