During last few days we're experiencing some delay in website stmp provider channel.
Some notification email from the website might not reaching containers.
We're working on a definitive solution.
I used Galaxy tab and tested some pdf from real magazines, and the reader does not seem to preload the next page. Therefore it felt slow when changing page. Is it possible to make the reader preload the next page?
The second question I encountered is that when on tablet, changing page on the reader requires a big swipe (long-distance swipe) in order to go to the next page. Is it possible to shorten the swiping distance?
With our internal tests we saw slow rendering performances opening PDFs files with a lot of high res, not optimized images and pictures.
By the way actually, doing a performances comparison with other available rendering engine we with our PDFViewer has good performances.
Are the magazines you are writing about freely distributable? May you send us one of them? We would like to do some tests on it, maybe looking at others reader again.
To send us big files write a direct email with a download link (our mailboxes should accept 10mb attachments and no more). If you don't own web space and don't want to adopt a free transfer service as wetransfer, let me know: I'll ask collegue to open a temporary ftp area.
You can please elaborate more? Do you mean your PDFViewer does not support it yet and we should implement our own page read-ahead chache system? Or there is a parameter we can enable it? We also would love to see this feature available to PDFViewer SDK as it's essential to our app.