Hi,
Following features would be nice in the high level classes:
1. Annotation Animations
If I view a PDF with for example an image with a URL, there is a transparant blue color over that rectangle. It would be nice if we could "set" the color of these Annotations (instead of the deault transparant blue). So basically creating a setter to get access to the Color value for this transparant Annotation layer.
What I actually want to achieve is to only show this semi transparant layer for a few seconds. Because the semi transparant layer is "messing up" the nice pictures, but by showing them for a few seconds the user knows where he can click. If there is a setter for this Color value, I can easily create a asynctask which puts that value on full transparant after a few seconds.
2. Landscape Mode
I know it's already requested by different persons here, but a 2 page landscape mode would be very nice.
3. Caching
You have more and more tablets with enough memory. t would be nice to already render some PDF pages in memory to speed up the scrolling between the previous or next pages. It would be much quicker.
I noticed that the Adobe PDF viewer is faster in viewing the next pages, however, when I go to a page much further, they don't show up immediately, which makes me believe that Adobe is caching the next pages, which is very nice.
In practice:
you can have for example 4 pages in memory:
-) current-1
-) current
-) current+1
-) current+2
If you go to the next page, you put the current page in "current-1", you show the "current+1" (= next page) immediately, you put the "current+2" object in "current+1" and you render the new "current+2" while the user is reading his PDF page.
REMARK:
I know that all of these functionalities can be implemented by ourselves using the low level classes.
The problem is that a lot of the added value of this SDK is in the high level (closed) classes, which implement already a lot of functionality for us. (using the low lvl classes makes this much complexer for a lot of people)
Regards,
Matt