I see I forgot to finish one line of thought mid-sentence.

As for the mentioned modules approx-string-match-js, dom-node-iterator,
dom-seek, dom-anchor-text-position; they all seem to fit in the project
scope, but feel a bit like an arbitrary collection of modules. Do you
have, or else shall we perhaps create, an overview of the modules we
want to create, and how they relate to each other? That way we would
have a clear reason why we have and maintain each module. In the
attached graph, I sketched the relations between the mentioned modules
(as I understand them), while already adding two hypothetical candidates
in grey.

— Gerben


On 6/27/19 2:53 PM, Gerben wrote:
> On 6/23/19 2:15 AM, Randall Leeds wrote:
>> […]
>>
>> Questions for Library Authors
>>
>> Gerben, would you be interested in bringing dom-highlight-range into
>> the project? We have an open issue [4] to build a highlighter.
>> Benjamin and I discussed at I Annotate that it would be immensely
>> valuable for users to have even a simple implementation. Your project
>> is already a dependency of the Apache Annotator demo, and its LICENSE
>> [5] credits dom-anchor-text-position.
> Sure, I’d be happy to group such modules under the Annotator umbrella. I
> agree it is valuable to have a highlighting tool available off-the-shelf
> (‘batteries included’), even if it may not be as generic/unopinionated
> as we would like other ‘core’ modules to be.
>
> I would not mind changing the name if that would be desired. Also both
> the API and implementation of the module could use some revision (I
> think this was my very first javascript module), but that could also
> happen after adopting it (e.g. use <mark> instead of <span>, make it an
> ES6 module, possibly return an object rather than just a cleanup
> function, …).
>
>> […]
> As for the mentioned modules approx-string-match-js, dom-node-iterator,
> dom-seek, dom-anchor-text-position;
>> Licensing Questions
>> […]
>> In the case of dom-highlight-range, Gerben is the sole author.
> A piece of it was copied from you (Randall). The rest I put out in the
> public domain, I hope that simplifies things.
>> […]
>
>

Attachment: modules-overview.dot
Description: application/msword-template

Reply via email to