[annotator-dev] About the future of the Range implementation
riccardo.tasso at gmail.com
Wed Jun 18 06:21:25 UTC 2014
Just a question: why did you choose xpath instead of css selector which are
parsed by jquery?
implemented an xpath finder in annotator, but probably it would be usefull
to have it as a separate component too.
2014-06-18 6:40 GMT+02:00 Randall Leeds <tilgovi at hypothes.is>:
> On Jun 17, 2014 7:07 PM, "Kristof Csillag" <csillag at hypothes.is> wrote:
> > On 2014-06-11 20:50, Randall Leeds wrote:
> > > +1 to releasing Range as a separate module.
> > Here is the first draft:
> > https://www.npmjs.org/package/xpath-range
> Nice. Hurray!
> - Vendor libs can be dropped. Markdown is definitely not part of this.
> wgxp can also be left out. I think it's not the responsibility of this
> library. We might debate that, but generally I'm of the opinion that
> applications, not libraries, should take care of their polyfills.
> - Instead of the postinstall step, coffee should be a dev dependency and
> the compilation should happen before publishing to npm.
> Happy to help however I can.
> annotator-dev mailing list
> annotator-dev at lists.okfn.org
> Unsubscribe: https://lists.okfn.org/mailman/options/annotator-dev
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the annotator-dev