Quote:
Originally Posted by kguil
Now, and I haven't put too much thought in this yet, I am considering an option to let readers choose their own basis for "words per page". For instance, you might rather define a page as having 350 words than accept my default of 250.
|
Some may like percentage, some may like a page count calculated in a particular way. I'm more for pages since like with paged viewing and real books, memory of what page, even if it's "faux" might be better triggered much like page position such as left/right. Like with other questions and options, such as those for the header/footer, they will complicate the UI and of course, it's your choice of how usable, popular, and sellable you want M3 to be. As mentioned before, I'm ok with waiting for any particular feature until you can find an elegant way, and I'm not for adding in everything that can be possibly imagined. Despite however simple or complicated the app becomes, I'm always concerned about what is most used remaining quick to see and access.
As for calculating pages, I'm not sure if you've considered. Agree, though everyone isn't going to, that # of pages per device remains the same. Considering how one might change font size, line-height, margins, etc, how about calculating pagination of a web view given some particular dimensions? While they vary, picking some size such as mass-market, paperback, hardcover, or paper size is another possibility.