>> I would like to learn more about the tradeoffs between stateful >> and stateless drawing APIs. If anyone can point me to a resource >> about this, I would be grateful.
> http://robert.ocallahan.org/2011/09/graphics-api-design.html > FWIW I don't think any of this affects Mozilla. We aren't going to use the > standard C++ graphics library ... unless it ends up being Moz2D or something > exactly like it :-). I summarized what happened at the SG13 meeting in my blog post about the committee meeting [1]. One interesting point that came up is that, since the thing being standardized is cairo's interface, not its implementation, the inefficiency that arises by having to go through cairo's public stateful layer, then its internal stateless layer, and then a backend library's stateful layer, can be avoided - an implementer can simply implement the standard (stateful) interface directly in terms of the stateful backend interface. Also, as I mention in my blog post, while the cairo proposal is being actively worked on and SG13 likes its direction, it's not too late to bring forward a competing proposal. If someone is interesting in writing a proposal based on Moz2D, I would be happy to present it at the next meeting. Cheers, Botond [1] http://botondballo.wordpress.com/2014/02/22/trip-report-c-standards-committee-meeting-in-issaquah-february-2014/#sg13 _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
