Just wanted to chime in as one of the Annotator maintainers.
We've been working on Annotator 2 for a while, in fits and starts, but
we're going to have a conversation about scoping the release sometime
within the month with an eye toward identifying and eliminating superfluous
things that we iterate on after 2.0 comes out.
However, one thing that is done already is a separation of the highlighter
into a plugin. Nick Stenning, one of the other maintainers, has also
started experimenting with an SVG-layer based approach to arbitrary text
overlays called "marks". It's very early and I hope I'm not putting him on
the spot to share it at this point. You can find that here:
https://github.com/nickstenning/marks
i fully expect that marks or something like it will replace the default
highlighter in Annotator. If there's anything we can do to collaborate with
PDF.js to help make your annotation story easier, please stay in touch.
Nick and I both work at Hypothesis (
https://hypothesis) and we've done some
serious twisting around Annotator to get something that works on top of
PDF.js, but we can and should create a much better story for the
interaction here.
Personally, I would like to see us tapping into annotation APIs in PDF.js
to surface out-of-band annotations from our network so that PDF.js can
handle the display.
If Annotator or, more likely, some smaller component like marks can help
with the display layer, I'd be thrilled. That would be a sensible
composition of components to me.
On Tue, Mar 10, 2015 at 10:41 PM, <
dav...@gmail.com> wrote:
> On Wednesday, September 24, 2014 at 7:19:39 AM UTC+5:30, vivek madkaikar
> wrote: