Quote:
Originally Posted by =X=
I've seen two implementations, one that crops only the margins and the other that crops on the paragraph doubled tapped on.
|
The first is probably easier to implement.
But I really like the second. It fits with my feel for the double tap as a zoom gesture. I suppose how it works in practice depends on the shape of the paragraph, etc. And if you double tap on an image, I suppose it will fill the image?
I wonder how it would work on a pdf where the text is implemented in images (e.g., some scanned books). I suppose it would zoom in to wherever the boundaries of the whole image are? One question to ask is this: In pdfs where the text is implemented in images, are the images all one piece, or are they tiled? If tiled, we might get wrong behavior if we zoom in on the current image. Some experimenting is worthwhile.
I fear that implementing this will require us to get under the hood on the muPDF code that is used for rendering, and modify that code. Currently, we use the muPDF code unmodified, which is great since we can easily upgrade the render engine as new muPDF code comes in (only changing it a little if the exposed API changes).
Maybe the changes would be just a matter of adding a new dummy fitz rendering device, akin to the render-to-text device. Nevermind: just thinking out loud.
Quote:
|
Ha Ha fair enough, I guess it's just a matter of opinion. I'm so use to pinch to zoom it's hard for me to navigate without it. I keep on sliding my fingers expecting it to resize, with no avail.
|
I can imagine how one could get used to it.
There are also possible patent issues. My understanding is that Apple's patent doesn't apply to a simple pinch zoom, but only to more complicated pairs of gestures, but I am not a patent lawyer. There would also be the issue of making sure that we're OK patent-wise globally, since some of the APV developers may be in other countries.
There may also be technical issues. Our rendering is still sort of slow and we achieve acceptable downward scrolling only by pre-rendering forward. That won't work for zooming. I suppose that for zooming in, we could simply blow up the tiles we have rendered, and then replace them with fresh tiles as soon as these become available. The effect might be really ugly. Zooming out would be even more problematic.
In any case, I may wait for the zoom enhancements until we have the render speed and memory use issues under control, and so these UI things might not make it into 0.3.0.
I should note that for all the texts I read, there isn't much of a zoom issue. I just zoom in past the page margins, and can read the whole page just fine in portrait on my 480x854 4.3" screen. I can imagine that if a book used particularly small font, or my eyesight were not as sharp (and one day it won't be), this wouldn't be so easy.