Excellent presentation of the library. After reading the source, I am struck with how much of the code here is just one or two line wrappers; "convenience" functions that don't really do anything but pass on the arguments to another function or set or get a property.
I'm not a big fan of thin API wrappers like this. Why not dispense will all that code and let your library users access the underlying properties and methods instead? The library would be smaller, simpler, and faster.
Please consider this library as an invitation for web devs to dive into html-based multimedia. Its main goal is to highlight the ability to do such things.
It is quite clear that Sprite3D will never reach the level of libraries like Three.js or PaperJS.
I'm not a big fan of thin API wrappers like this. Why not dispense will all that code and let your library users access the underlying properties and methods instead? The library would be smaller, simpler, and faster.