- From: Fabrice Robinet <cmg473@motorola.com>
- Date: Thu, 12 Jan 2012 11:53:41 -0800
- To: Gregg Tavares (wrk) <gman@google.com>
- Cc: public-fx@w3.org
Looks like a de-facto standard but could be fine... I am - of course - not against providing more possibilities :), That would open fantastic possibilities.. Either way, adding 24 new optional uniforms in the spec wether they are easy to implement or not, In comparison with the existing set, might sound like a heavy addition to the spec. So what's the take on spec editors on this ? On Jan 12, 2012, at 11:20 AM, Gregg Tavares (wrk) wrote: > Once you add in CSS shaders you have no idea what they will be used for > and what kinds of effects people will try to make. > > There is already a standard for shaders in the from of Standard Annotations and Semantics that > shader editors already use. It's used in NVidia's FX Composer. It's used in AMD's Render Monkey, > It's used in several other shader editors. It provides 24 standard matrices. Why diverge from this standard? > > 24 is not that many. It's trivial to implement. They can be computed on demand only when > needed and cached if needed again for the same view. They are standard. They cover more > needs. > >
Received on Saturday, 14 January 2012 01:15:34 UTC