Re: [filters] Custom filter functions proposal

Hi Lea, all,

I like the idea. If we go this route, then we should have a common solution for custom SVG filters and for shaders. It would be more consistent, I think to have the same syntax for custom filters, no matter how the filter itself is defined.

I like the approach of using an @filter rule, but I am not clear on what the syntax would look like to define, say, three parameters (one number, one point and one array) with their names and defaults.

Cheers,
Vincent
From: Lea Verou <leaverou@gmail.com<mailto:leaverou@gmail.com>>
Date: Mon, 20 Feb 2012 15:00:35 -0800
To: Dean Jackson <dino@apple.com<mailto:dino@apple.com>>
Cc: Lea Verou <leaverou@gmail.com<mailto:leaverou@gmail.com>>, Rik Cabanier <cabanier@gmail.com<mailto:cabanier@gmail.com>>, "public-fx@w3.org<mailto:public-fx@w3.org>" <public-fx@w3.org<mailto:public-fx@w3.org>>
Subject: Re: [filters] Custom filter functions proposal

On 20/2/12 22:59, Dean Jackson wrote:
I agree this is a good idea. We had considered proposing this from the start, but figured it would slow the process down (I expect we would spend a lot of time iterating over syntax). It's also a change to parsing in SVG.

I hope we can get to it soon.

Dean
The change in SVG parsing is not tied to this proposal though, it needs
to be done anyway for SVG Parameters. SVG Parameters is something badly
needed in SVG anyway and I'd love to see development continue for that
spec. Authors are currently abusing Webfonts to get behavior that would
be much better implemented with SVG Parameters (i.e. utlizing the same
vector icon with different colors in different places).

--
Lea Verou (http://lea.verou.me | @LeaVerou)