W3C home > Mailing lists > Public > www-style@w3.org > March 2014

RE: [css-images] Generated noise image

From: David Dailey <ddailey@zoominternet.net>
Date: Sat, 8 Mar 2014 13:52:39 -0500
To: "'Tab Atkins Jr.'" <jackalmage@gmail.com>
Cc: "'Dirk Schulze'" <dschulze@adobe.com>, "'www-style list'" <www-style@w3.org>, "'www-svg'" <www-svg@w3.org>
Message-ID: <001c01cf3aff$97a63f40$c6f2bdc0$@net>
On  Friday, March 07, 2014 5:21 PM
Tab Atkins Jr. wrote

To: David Dailey
Cc: Dirk Schulze; www-style list; www-svg
Subject: Re: [css-images] Generated noise image

On Fri, Mar 7, 2014 at 1:58 PM, David Dailey <ddailey@zoominternet.net> wrote:
>> Not sure why this should be a CSS thing instead of a filter or 
>> filter-attribute. Would it be useable as a part of a standard filter 
>> chain in SVG?

>SVG's filter system, for some weird historical reason, has a few "filters" that are >actually paint servers - they have no inputs, and generate an image.  Turbulence is one, >for example. [...]

I guess I never found it too weird, since there didn't seem to be any other declarative way to bring randomness into a region. Now we have both <feTurbulence> and <random> [1], but other ways are definitely valuable for scene creation.

Tab continues:
>Rather than add new filters that commit the same mistake, we've discussed just adding them >as paint servers (or in CSS parlance, <image> values).  You can then use them in a filter >chain as normal, by painting an input with them.  It's possible that we can make it easier >to use a paint server more directly in a filter chain, too.

Out of curiosity, if this were done, are there ideas as to what the syntax would look like?

Is something like  <style> .myshapeclass{fillGaborNoise:4,5,22,'retort',false}
<svg><ellipse class=myshapeclass [...] /> sort of what ya'll had in mind (assuming there were some fillGaborNoise paint server that took a series of parameters)?


[1] http://cs.sru.edu/~ddailey/svg/RandomTalk.html 
Received on Saturday, 8 March 2014 18:53:19 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:14:38 UTC