Quote:
Originally Posted by cartesius
The page break issue: probably Adobe didn't care so much about the devices with a fixed viewport size, such as e-book readers. Their reader simply uses the whole window to display as much as it can and since there is no need to 'flip' the page one cannot realize it's page based. Should you care about this? No. You have right to ask for better. But, please, have some patience, this feature is still in its infancy. There are also some usability challenges posed by this need to avoid 'page waste' but that's a different story.
|
Reflowing one page at a time was a design decision on Adobe's part, and I'm not sure they were wrong to do it this way. The big advantage to the per-page approach when the reflowing is done in real time is that the reader has the option to refer back to the original page if the reflow goes wrong. It also allows the app to fail on a page by page basis (e.g. reflowing most pages, but displaying some only in full page mode). However, some of these advantages could be kept without displaying a partial screen, e.g. by having the last screen on one page include reflowed text from the next page - perhaps after a visible page break (e.g. line across the screen).