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: Vincent Hardy <vhardy@adobe.com>
Date: Fri, 5 Aug 2011 16:36:35 -0700
To: "Tab Atkins Jr." <jackalmage@gmail.com>, Cyril Concolato <cyril.concolato@telecom-paristech.fr>
CC: SVG Working Group WG <public-svg-wg@w3.org>
Message-ID: <CA61CC5E.EE07%vhardy@adobe.com>


On 8/5/11 10:24 AM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote:

>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>?  

Originally, <solidColor> was introduced because solid colors where the
only type of paint server that could only used by value and not by
reference. A gradient could be shared by multiple elements, not a solid
color.

>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.
>
>~TJ
>
Received on Friday, 5 August 2011 23:37:14 UTC

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