On 22/03/2013, at 4:14 AM, Gregg Tavares <email@example.com> wrote:
There already is a matrix library built into the browser. We can't remove it. What the proposal on public-fx is trying to address is this:
1. Avoid the EXTREMELY costly conversion to/from a CSS string representation for CSS and SVG transforms
2. Produce an API that is compatible with the existing, implemented and unchangeable Matrix API that's in the browser
3. Given that 2 has some convenience methods for 2d transforms on matrices, and we're seeing lots of people do the same with 3d (but using strings!), extend the API to cover basic 3d transform operations
4. Be at least as fast as a pure JS approach (or comparable for typical uses)
5. Be built-in (no external download)
Despite arguing at length on the public-fx list, I'm very open to coming up with *any* solution that addresses the points above satisfactorily. If we can produce something that is helpful to WebGL as well, that would be awesome. But I'm getting the impression from this thread that you'd prefer custom JS libraries, which is fine. In which case, this API is irrelevant to you (and maybe the naming is the issue - should it be prefixed?).
In other words, since this API is an extension of something that already exists in the browser, it's not making WebGL content do anything different, and you're free to chose whatever solution you want.
Also note that the proposal isn't even an official public draft yet, so it can go through massive changes.