W3C home > Mailing lists > Public > public-svg-wg@w3.org > January to March 2009

RE: Vector effects module

From: Alexander Adam <alexander.adam@examotion.com>
Date: Fri, 13 Feb 2009 08:45:57 +0100
To: "'Chris Lilley'" <chris@w3.org>, <public-svg-wg@w3.org>
Message-ID: <F17FAB2D47CE48D9A9E813EB1C750394@DellPM6300>

Hi All,

I am still quite curious whether we really need union, intersect and
include? Shouldn't that be the part the authoring tool does? I mean, such
operations are very costly in time. Or is it just for the ability to for
example dynamically merge pathes together?

About the marker issue -- I think we should seriously consider to allow
veMarker for SVGT 1.2 as well. Just the default behaviour should exclude
veMarker for such languages but if an author really wants to use them then
he should go ahead.. And frankly, markers should be cheaper for rendering
than for example union or intersection of complex pathes.

mfG / Regards,
Alexander Adam
--
Geschäftsführer / CEO
 
examotion GmbH
Ostendstraße 115
90482 Nürnberg, Germany

Fon: +49 911 - 504901-11
Fax: +49 911 - 504901-20
 
E-Mail: alexander.adam@examotion.com
Web: http://www.examotion.com
 
Geschäftsführer: Alexander Adam
Amtsgericht Nürnberg HRB Nr.: 23803
Gerichtsstandort: Nürnberg
 

--------------------------------------------------
LEGAL DISCLAIMER: The information in this email is confidential and may be
legally privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted to be
taken in reliance on it, is prohibited and may be unlawful.
--------------------------------------------------
 
> -----Original Message-----
> From: public-svg-wg-request@w3.org [mailto:public-svg-wg-request@w3.org]
> On Behalf Of Chris Lilley
> Sent: Donnerstag, 12. Februar 2009 20:02
> To: public-svg-wg@w3.org
> Subject: Vector effects module
> 
> 
> Hello public-svg-wg,
> 
> Its still horribly messy, particularly the primer (although that is still
> the best place to start reading). The langauge spec is in better shape. I
> have tried to follow the coding style used in SVGT 1.2 and in the filters
> module, but there are probably some things wrong there. There is a chunk
> of explanatory matter that is still in my head struggling to get out.
> 
> I have not tried to run master2publish on this.
> 
> There are svg images, with png fallback, and also another directory where
> the sources for those (Inkscape svg) are stored. To foild the server
> trying to conneg and messing things up, the svg and pg are in separate
> directories.
> 
> The RNG from the original SVG 1.2 Full chapter 9 has been stripped out and
> attribute definitions added in the current style. I have not yet put the
> RNG into separate files, far less tried to validate any examples. The
> examples are all inline currently, but should be split into separate files
> and included by master2publish.
> 
> The test suite does not exist yet.
> 
> There are a bunch of editorial notes.
> 
> Enjoy.
> http://dev.w3.org/SVG/modules/vectoreffects/master/SVGVectorEffectsPrimer.
> html
> 
> http://dev.w3.org/SVG/modules/vectoreffects/master/SVGVectorEffects.html
> 
> 
> --
>  Chris Lilley                    mailto:chris@w3.org
>  Technical Director, Interaction Domain
>  W3C Graphics Activity Lead
>  Co-Chair, W3C Hypertext CG
> 
Received on Friday, 13 February 2009 07:47:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 13 February 2009 07:47:16 GMT