W3C home > Mailing lists > Public > www-svg@w3.org > July 2000

Re(2): SVGColor Inheritance.

From: Jon Ferraiolo <jferraio@Adobe.COM>
Date: Wed, 05 Jul 2000 14:04:28 -0700
Message-Id: <200007052101.OAA14113@mail-345.corp.Adobe.COM>
To: bbrodie@savagesoftware.com (Blaine Brodie)
Cc: www-svg@w3.org
I believe that the factory methods createSVGColor() and createSVGPaint()
need to be eliminated. There is no ability to create any of the CSS_CUSTOM
interfaces in DOM2; you can only retrieve objects of type
CSS2BackgroundPosition or CSS2Cursor; you have no creation facilities.

If createSVGColor() and createSVGPaint() are eliminated, I believe we are OK.

Jon Ferraiolo
SVG Editor
Adobe Systems Incorporated

At 06:30 PM 7/4/00 -0700, Blaine Brodie wrote:
>>I believe you have analyzed things correctly.
>>Not only SVGColor, but also SVGPaint, needs to inherit from CSSValue. We
>>will fix the spec at our earliest opportunity. 
>>Thanks for the report.
>>Jon Ferraiolo
>>SVG Editor
>>Adobe Systems Incorporated
>After looking at the spec. again I noticed that there are two factory
>methods named createSVGColor() and createSVGPaint(). There could be a
>problem if SVGColor inherits from CSSValue, since these methods create
>their objects outside the context of a CSS property.  This means the user
>will not be able to use the CSSValue::setCssText() method since there will
>be no property grammar to parse against.  Perhaps a better solution,
>rather than having SVGColor inherit from CSSValue, would be to do
>something like the following, which is similar to how CSSPrimitiveValue
>retrieves its RGBColor, Rect and Counter objects.
>	SVGCSSValue : CSSValue 			// where SVGCSSValue has a valueType of
>	{ 
>		SVGColor getSVGColor(); 	
>	};
Received on Wednesday, 5 July 2000 17:02:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:53:50 UTC