Just a question: why did you choose xpath instead of css selector which are parsed by jquery?
Is there a javascript library which parses xpath? If I remember well you implemented an xpath finder in annotator, but probably it would be usefull to have it as a separate component too. Cheers, Riccardo 2014-06-18 6:40 GMT+02:00 Randall Leeds <[email protected]>: > On Jun 17, 2014 7:07 PM, "Kristof Csillag" <[email protected]> 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! > > Notes: > > - 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 > [email protected] > https://lists.okfn.org/mailman/listinfo/annotator-dev > Unsubscribe: https://lists.okfn.org/mailman/options/annotator-dev > >
_______________________________________________ annotator-dev mailing list [email protected] https://lists.okfn.org/mailman/listinfo/annotator-dev Unsubscribe: https://lists.okfn.org/mailman/options/annotator-dev
