[annotator-dev] Image annotation

[Randall Leeds]

On Sun, Oct 12, 2014 at 2:23 PM, Kristof Csillag <csillag at hypothes.is>
wrote:

> On 2014-10-12 19:50, Nick Stenning wrote:
> > On Sun, Oct 12, 2014, at 18:22, Randall Leeds wrote:
> >> Another potentially useful direction to go would be to separate the
> steps
> >> of identifying and highlighting the anchors. It should be possible to
> use
> >> the selector implementation to get the image element and bounding box
> >> information. With OS integration that'd probably be adjusted for zoom
> and
> >> pan.
> > Randall is bang on in regard to how this works in Annotator 2.0.
>
> Right, so this means that we managed to do quote a bit of parallel work
> here :)
>
>
I'm not so sure. Annotator 2.0 doesn't provide a framework for configuring
a collection of implementations. There are no strategies, etc. There is no
defined coupling between a core and these components (selection events,
etc).

The default UI provides one, specific interaction between a particular set
of selection, anchoring, and highlighting components for text, but it is
not pluggable. I think this is a good thing right now.


> Selecting an area for annotation and drawing a loaded annotation are
> > entirely decoupled from one another.
> ditto.
>
> Let's chat about how to best merge these really soon.
>

I think all that needs to be done, as I've talked about a lot when we
discussed our roadmap for getting away from our fork, is to expose each of
our components in a way such that they're packaged independently of
Annotator.

I'm not thrilled with the set of events we have in our fork right now and
the simplistic way that anchoring strategies are are applied sequentially.

Let's start by composing components by hand rather than trying to implement
a generic algorithm that composes them for us based on configuration.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/annotator-dev/attachments/20141012/91b3b5d1/attachment-0004.html>