W3C home > Mailing lists > Public > public-svg-wg@w3.org > July to September 2011

Re: List of features from SVG Tiny 1.2 not in SVG 1.1

From: Cyril Concolato <cyril.concolato@telecom-paristech.fr>
Date: Sat, 06 Aug 2011 13:35:34 +0200
Message-ID: <4E3D2706.7040403@telecom-paristech.fr>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
CC: SVG Working Group WG <public-svg-wg@w3.org>
Le 05/08/2011 19:24, Tab Atkins Jr. a écrit :
> On Fri, Aug 5, 2011 at 4:08 AM, Cyril Concolato
> <cyril.concolato@telecom-paristech.fr>  wrote:
>> Hi all,
>> Following up on ACTION-3100, I've set up a page describing the features that
>> are in SVG Tiny 1.2 but not in SVG 1.1 2nd Ed. The page is here:
>> http://www.w3.org/Graphics/SVG/WG/wiki/SVG_Tiny_1.2_feature_backport
>> I may have missed some or made mistakes. Please review it and comment/modify
>> the page.
>> This closes the action.
> Small question related to this.
> Given that colors are already paint servers in SVG, what's the purpose
> of<solidColor>?  Is it solely to allow you to fill with a
> partially-transparent color?  If so, it seems like we could address
> this easily by just adopting the additional color functions defined in
> CSS.
I think the idea was to be able to define in a <defs> the color palette used in the scene to be able to modify or animate the palette in a single place. As Tav and Vincent said, we wanted to use solid colors (color and opacity) as gradients, and remember that CSS stylesheets are not mandatory in SVG Tiny 1.2.


Cyril Concolato
Maître de Conférences/Associate Professor
Groupe Multimedia/Multimedia Group
Telecom ParisTech
46 rue Barrault
75 013 Paris, France
Received on Saturday, 6 August 2011 11:35:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:20:13 UTC