- From: Jon Ferraiolo <jferraio@Adobe.COM>
- Date: Fri, 08 Sep 2000 10:19:06 -0700
- To: AndrewWatt2001@aol.com
- Cc: www-svg@w3.org
The SVG working group discussed having SVG support the 'z-index' property from CSS and decided against it for SVG 1.0, partly to avoid adding that extra bit of implementation complexity. Personally, I still agonize over whether 'z-index' should have been put into SVG 1.0. Definitely, the W3C should consider 'z-index' for future versions of SVG. Jon Ferraiolo SVG Editor Adobe Systems Incorporated At 04:02 AM 9/8/00 -0400, AndrewWatt2001@aol.com wrote: >In a message dated 07/09/00 23:07:25 GMT Daylight Time, >sdickson@savagesoftware.com writes: > > > Are there any plans to add alternative rendering order schemes? > > Currently, SVG documents are always rendered using the painter's algorithm > > only. To change the order in which objects are rendered, it is necessary > > to rearrange the objects within the document itself, a potentially costly > > and time-consuming process. > > S. > > > >Steve, > >I guess it partly depends on what you mean by "costly" and "time-consuming". >But, in principle, XSLT would allow you to reorder elements/objects within >SVG source without huge difficulty. > >How costly or time consuming the use of XSLT would be would depend partly on >the complexity of the SVG source document, available XSLT skills and whether >there was any pattern of reordering required (i.e. could you reuse XSLT >template stylesheets). > >Is there some technical reason why XSLT wouldn't meet your present needs? > >Andrew Watt
Received on Friday, 8 September 2000 13:33:01 UTC