View Single Post
Old 07-10-2020, 03:30 AM   #15
democrite
Evangelist
democrite will give the Devil his due.democrite will give the Devil his due.democrite will give the Devil his due.democrite will give the Devil his due.democrite will give the Devil his due.democrite will give the Devil his due.democrite will give the Devil his due.democrite will give the Devil his due.democrite will give the Devil his due.democrite will give the Devil his due.democrite will give the Devil his due.
 
Posts: 441
Karma: 77256
Join Date: Sep 2011
Device: none
Flow mode is for me too very natural on a screen. We view web pages as such; many perhaps most view PDFs as such. Why not EPUB? Multiple viewers have it. iOS Books. Now Kindle for iOS and perhaps Android. Google Play app not yet. eReaders? Screen tech perhaps does not allow for such.

Merging or conversion is not quite possible in many cases. Not everyone reads simple so called fiction. Many works have multiple footnotes, references, etc., and such may not survive a merge. The Apple iOS solution was to add a control type to iOS itself of an array of views, web views in the case of Books, and render views as needed. Not possible for calibre? Perhaps. Possible to have lets say a recyclable array of three or x number of views such that as one scrolls, the next and previous views are loaded such as if one is at some file boundary more than one can be displayed stacked, and if one scrolls to a position, the view length is already calculated and then loaded? Maybe possible. A lot of work? Could be. I continue to believe flow is the natural way to view an ebook, at least on desktop, and if it's not used more for eBooks, it's perhaps the difficulty of implementing such.
democrite is offline   Reply With Quote