View Single Post
Old 04-04-2008, 03:57 AM   #3
Sparrow
Wizard
Sparrow ought to be getting tired of karma fortunes by now.Sparrow ought to be getting tired of karma fortunes by now.Sparrow ought to be getting tired of karma fortunes by now.Sparrow ought to be getting tired of karma fortunes by now.Sparrow ought to be getting tired of karma fortunes by now.Sparrow ought to be getting tired of karma fortunes by now.Sparrow ought to be getting tired of karma fortunes by now.Sparrow ought to be getting tired of karma fortunes by now.Sparrow ought to be getting tired of karma fortunes by now.Sparrow ought to be getting tired of karma fortunes by now.Sparrow ought to be getting tired of karma fortunes by now.
 
Posts: 4,395
Karma: 1358132
Join Date: Nov 2007
Location: UK
Device: Palm TX, CyBook Gen3
Quote:
Originally Posted by bob_ninja View Post
The 1st question is what is a page in the 1st place. Well it is the display device, or browser window, whatever is displaying content. Thus page is defined by our display.
Maybe one approach could be to break the connection between a 'page' and the screen display, so that a page could span more (or less) than one screen and rendering calculations aren't required.
If pagination was somehow embedded in the file it would produce stable and consistent page numbering.
Of course then an attempt to 'go to page 136' might only display the first part of the page on the screen; but it would only be a key press or two to get to the bit of the page you wanted (probably no less efficient than the current method).
This approach would also maintain consistency of page numbering regardless of display format and device, and reduce the workload for the device.
Sparrow is offline   Reply With Quote