Hi,
I did a hack that acted like that some time back. But that resulted in some much reduced functionality regarding page content, e.g. only one image per page, no page caching etc. I can't (and don't want to) disclose the code here, but the basic idea was like this:
The whole book actually only has one page, with a specially written element on each of the two pagesides. Those elements displayed the one image per page. Whenever the user moved the cursor close to one of the page's edges, the book would immediately jump to the first or last page, respectively, to allow turning the page. Depending on which side of the page was lifted the displayed content of the "backside" page element would also change accordingly.
As you see, this completely works around the internal loading and page element functionality though, so that's why you'll lose quite some features.
I'd be interested in hearing other people's ideas on alternative solutions, though, myself
