W3C home > Mailing lists > Public > www-svg@w3.org > February 2011

Re: SVG 1.2 Vector Effects

From: Chris Lilley <chris@w3.org>
Date: Fri, 18 Feb 2011 22:37:09 +0100
Message-ID: <32339707.20110218223709@w3.org>
To: ddailey@zoominternet.net
CC: www-svg@w3.org, yan.li@sru.edu, yanli@scnu.edu.cn, david.dailey@sru.edu
On Friday, February 18, 2011, 2:32:57 PM, ddailey wrote:

dzn>  
dzn>  A colleague and I are working on a paper together and have some
dzn> questions about SVG1.2 and, specifically, the vector effects parts:
dzn>  1. I gather that SVG 1.2 is still a working draft.

It is a collection of modules, which are working drafts, plus a profile (Tiny 1.2) which is  Recommendation.

dzn>  Will it
dzn> become a recommendation or will the WG just bypass it and move to
dzn> 2.0? 

Move directly to 2.0

dzn> And if so, will Vector Effects become a part of that? 

I would hope so. That depends though on spec development, test suite development, and implementor uptake (as it does with all the modules).

dzn>  2. What progress, if any, do we know of browsers or other user
dzn> agents actually implementing Vector Effects? I know that Opera
dzn> has implemented some very important parts of 1.2. Is there any
dzn> inventory of cross-browser progress on the various parts of 1.2? 

I'm not aware of any inventory of cross-browser progress on these modules. That is something that we want to track, though.

dzn>  3. Are there JavaScript implementations available as an API or
dzn> something for doing the various things discussed in Vector
dzn> Effects? I have a notion (albeit fuzzy) that as specs are moved
dzn> along the path from working draft to recommendation, they
dzn> frequently find some instantiation in actual code somewhere.


There do need to be implementations for a spec to exit the CR phase.

JavaScript-based prototyping often precedes the native implementation phase.

dzn>  4. A number of the images in the vector effects primer are
dzn> broken :
dzn> http://dev.w3.org/SVG/modules/vectoreffects/master/SVGVectorEffectsPrimer.html
dzn> . Any chance those could be repaired?

It would be helpful if you indicated which images are broken and in which browser (name/version/os) you see them as broken, and what symptoms of brokenness you observe.

Checking just now in Firefox (minefield 4.0b12pre, WinXP) I see nine images, which have the expected content.


-- 
 Chris Lilley   Technical Director, Interaction Domain                 
 W3C Graphics Activity Lead, Fonts Activity Lead
 Co-Chair, W3C Hypertext CG
 Member, CSS, WebFonts, SVG Working Groups
Received on Friday, 18 February 2011 21:38:34 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:47 GMT