4 ms·
Each flip actually needs to render 2 pages if it's going to be like a real book. And you need to handle about 5 flips per second or it's never going to be as f
by fuzzfactor 2y ago
Each flip actually needs to render 2 pages if it's going to be like a real book.
And you need to handle about 5 flips per second or it's never going to be as fast as a real book..
Smaller pages are naturally easier to flip faster than large ones physically, you would expect that from an ebook too.
I think a realistic test is using the physical Grainger catalog as a benchmark.
These pages are small and they flip fast.
At a nominal 4 flips per second you get to page 100 in under 15 seconds, with every graphic on every page perfectly rendered before the next flip appears in its entirety.
This equals 250 milliseconds per flip or 125 milliseconds per page.
With a real book the rendering requires zero milliseconds, you can take about 50 milliseconds to accommodate the visual discrepancy from the previous image, leaving you with about 200 milliseconds to take in everything that's there before the next flip.
This is pretty nominal for fast thorough paging or searching. Somehow or another you have to be able to see every detail faster than you can comprehend it all during paging, and be physically able to control paging speed according to what you see as you go along, so you have complete control of your perception and desired comprehension level on a dynamic basis.
If your ebook can't do this yet you've got work to do.
- llhh 2y agoAs a compromise, perhaps a different implementation could be considered: instead of rendering every page during the flipping process, the content around page 100 could be rendered only after rapidly flipping to that point.