Perhaps follow the Kiva API?

[corranwebster]

What you are doing is very close to this API already, and I am not suggesting a dependency, merely API compatibility. But if you were to do this you would get Chaco plotting on the ipycanvas essentially for free.

See https://github.com/enthought/enable/blob/master/kiva/abstract_graphics_context.py for the ABC that defines the API.

[martinRenou]

But if you were to do this you would get Chaco plotting on the ipycanvas essentially for free

Interesting! Right now I am trying to expose the Web Canvas API, so I'm keeping the same function names (only I switch to snake case). I will probably generate that API from the spec automatically instead of typing it.

@wolfv also had the idea of using the web canvas for drawing matplotlib plots. That would be a similar work I guess.

Thanks for the idea! I will give it some thought. Maybe having multiple available APIs would be a good idea? ipycanvas would use the Web Canvas API by default but could use other APIs if the user wants.

How easy do you think it would be to tell Chaco to use the ipycanvas context instead of the kiva one?