W3C home > Mailing lists > Public > www-style@w3.org > October 2011

Re: [css-shaders] CSS shaders for custom filters (ACTION-3072)

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 3 Oct 2011 14:30:34 -0700
Message-ID: <CAAWBYDBspYNq8wkk1GsZ5x30S4QFG5G-7pr3o-T3V=isfCzksQ@mail.gmail.com>
To: Charles Pritchard <chuck@jumis.com>
Cc: "Gregg Tavares (wrk)" <gman@google.com>, "www-style@w3.org" <www-style@w3.org>
On Mon, Oct 3, 2011 at 2:23 PM, Charles Pritchard <chuck@jumis.com> wrote:
> On Oct 3, 2011, at 1:16 PM, "Gregg Tavares (wrk)" <gman@google.com> wrote:
>> What about mouse input?
>> It seems like for this proposal to actually work as other CSS works
>> you'd need to run mouse and touch events through the vertex shader so
>> that you get the mouse coordinates translated through the shader.
>> Yes? No?
> CSSMatrix and transform3d are a good start. A method returning a CSSMatrix
> object may be enough.
> The following would help me to track elements and mouse clicks:
> CSSMatrix getMatrixFromBounds(x,y,[optional] width, height)
> 1. Use the canvas width and height as the limits, 2, return a css matrix.
> The author is responsible for using the matrix to translate points.

I don't understand what you mean.  A vertex shader is not, except in
trivial situations, equivalent to any predefined 3d transform, even
presented in the generic matrix form.

Received on Monday, 3 October 2011 21:31:21 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:50 UTC