Quote:
Originally Posted by mdmorrissey
Pardon me for saying so, but I would urge GiK, whoever or whatever that is, to concentrate on stability. I know people have different desires, but really, wrist-page-turning and autorotation should be way down the list of priorities.
|
The wrist page-turning version of FBReader doesn't come from the GiK; it comes from a separate Open Source effort. That's why its not bundled in the base firmware.
Pagination, on the other hand, is a core feature of readers. What the PB line does is they pre-paginates the book in the backgroud every time it loads or if you change settings. That is one reason why page turns on the PB readers is faster than other readers. Other readers do just-in-time pagination so they have to build the page up between the moment you tell it to page and the time the page shows up. Every time you rotate the screen or change margins, spacing, fonts or sizes, the pagination of the book changes.
What Kacir was alluding to was that that pre 15.2 versions repaginated *everytime* you went into settings or rotated the display. He is reporting that 152 is savvy enough to recognize some changes *don't* require repagination.
Improving the efficiency of CPU usage by the firmware (by not doing something that doesn't need doing) results in better performance, longer battery life (theoretically, anyway) and, ahem, marginally better stability.
This is a *good* thing for *everybody*, which is why he's suggesting it shouldn't be an undocumented feature.