Would be fine for you to get a dictionary with all the info
required to display the annotation (for example as an overlay
view)? Basically, this will expand on the -annotationsForPage:
method by returning more information in the case the annotation is
of type Text.
on 22 Aug, 2012 09:42 PM
We have purchased this toolkit for a client project and they
want to push a build live next week. This feature is a deal breaker
for the client. Is there a way you can give us an estimate on when
this might be supported? If not we may be forced to use another
toolkit for this project.
We are prepping the above mentioned solution. Due to the
structure of the pdf document, it require a bit of work to be done.
I'm confident I should be able to provide to you a testable
solution within 24-48 hours. I'll keep you up to date.
on 23 Aug, 2012 05:22 PM
That's great news. We really have a big push on this with our
client on a very high profile project. Please let me know if this
timeline changes. Also let me know when this is ready in GitHub.
We have added a function to get the entire annotation structure
as a Cocoa-friendly object, -cocoaAnnotationsForPage:.
The details are in the MFDOcumentManager's header.
We are also writing an implementation as Widget (FPKExtension) if
you are interested in playing with them, that will give some sort
of text annotation support out of the box.
I tried to make public the stream renderer for the annotation
appearance stream(s), but it has too many private dependencies
still. It's likely you have write your own if you are willing to
use the embedded appearance in the pdf annotation rather than
'force' the look of the annotation at application level.