On Sat, 2009-03-28 at 13:32 -0700, Joshua A. Andler wrote:
On Sat, 2009-03-28 at 13:17 +0000, john cliff wrote:
I'd be no less SVG compliant than Illustrator, which does exactly what I'm suggesting to get round this sort of issue. Its also what we do to blurs etc when we write them to PDF, so theres precedent in the codebase already...
Personally SVG is the means to the end, not the end in itself.
Same here. I do think your proposed bitmap solution is a good way to work around the problem of other SVG renderers (first thing that popped into my head too). As much as we all love SVG and standards, SVG evolves slowly. I'd argue that we should focus on making our program more standards compliant before we start pushing beyond the current standard, however, someone had a creative itch to scratch and they did (and will probably continue to if we support them).
I completely disagree on where this thread is going. I think of SVG like x86 byte code, it sucks in many ways, but by sticking with it we get lots of gains. For one, we have an entire committee who deals with compatibility issues for us :)
WRT the radial gradients I don't understand why the same techniques that Bulia came up with for the gradient meshes can't be used. I believe the attached file is roughly a radial gradient from black to white in the middle of a rectangle. And there's no reason we can't detect the meta data and render it in our own implementation in a faster way, but this should be vector in Firefox also.
--Ted
PS - View the file in Inkscape not RSVG. RSVG fails on this one :)
