[annotator-dev] About the future of the Range implementation

Randall Leeds tilgovi at hypothes.is
Wed Jun 11 18:50:22 UTC 2014

+1 to releasing Range as a separate module.

The best thing around besides ours seems to be Rangy and it unfortunately
seems to be acquiring more stuff, such as a highlighter.

A good Range package would be a great thing for the web dev community.
On Jun 11, 2014 8:18 AM, "Kristof Csillag" <csillag at hypothes.is> wrote:

> Hi all,
> As some of you already know, currently I am working on separating all
> the anchoring-related work that which Annotator does (both in the
> Upstream version, both in the Hypothes.is fork) into a separate library,
> which Annotator and other projects could use, but which can be developed
> independently.
> As a part of this problem, I need to have the current Range
> implementation (BrowserRange, NormalizedRange, SerializedRange) in that
> library, too.
> How would you feel like releasing this part (the Range implementation)
> as a separate NPM package, so that it can be plugged in easily wherever
> we need it?
>    Kristof
> _______________________________________________
> annotator-dev mailing list
> annotator-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/annotator-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/annotator-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/annotator-dev/attachments/20140611/11a8b7b3/attachment-0004.html>

More information about the annotator-dev mailing list