Library design/intent/future

[garyb]

This library currently defines all its own types and a bunch of specialized functions, completely independent from the rest of the spec-based web/dom libraries. Do we want to keep it as it is, or should we remove the stuff that duplicates work done elsewhere and just have it implement the Context2D interface as per https://www.w3.org/TR/2dcontext?

I'm fine with either, but if it's the latter, I'll be tempted to make a purescript-web-context2d library that is just the minimal thing, and then base this library on top of that, so at least it can share types with the rest of the web ecosystem.

[hdgarrood]

The latter option sounds good to me :)

[paf31]

The latter option sounds preferable in that it seems like it would be possible to keep the API of this library fairly constant, which I like because it is used in the book. Perhaps this library could even become a thin veneer over the web-canvas library and move back to contrib.

[garyb]

Ok, sounds like we have a plan then. I'll work something up and open a PR.