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

[Gergely, Ujvari]

I like Range being in a separate module.
About rangy, as I see, they do not really fix issues fast.

2014.06.11. 20:50 keltezéssel, Randall Leeds írta:
>
> +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
> <mailto: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 <mailto:annotator-dev at lists.okfn.org>
>     https://lists.okfn.org/mailman/listinfo/annotator-dev
>     Unsubscribe: https://lists.okfn.org/mailman/options/annotator-dev
>
>
>
> _______________________________________________
> 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/9be7cf2a/attachment-0004.html>