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

SVG 1.2 - Rendering Custom Content

From: Kevin Lindsey <kevin@kevlindev.com>
Date: Fri, 18 Jul 2003 17:26:07 -0500
Message-ID: <005401c34d7b$95722db0$6401a8c0@monkey>
To: <www-svg@w3.org>
SVG Working Group,

I have seen a few requests for feedback concerning RCC in SVG 1.2 but not much activity, so I'm throwing in my 2 cents.

Where to start...I am very excited by the possibilities of RCC.  I see it having a profound effect on SVG and its domain.  I have been trying to get SVG to do this very thing for years now.  This solution is both elegant and intuitive.

I do have concerns with speed of execution.  Specifically, I'm referring to the use of script to style complex custom elements.  As a simple example, imagine you have implemented border styles for your custom element.  Let's say you create a simple 3D effect using two lines (as path elements) of varying color on each side of the box.  Each time this element resizes, you will have to make 8 calls to setAttribute.  That in itself is not a problem, but when you have say 100 of these elements (not an unreasonable number), then you will make 800 calls.  Now imagine that all of this is happening while resizing a window (thinking layout manager here).  From my experience, the refresh rate becomes a bit slow.  It seems like the overhead of these calls could be avoided, but that would require something other than ECMAScript.

RCC is still too new in my mind to more impressions than those listed above.  Overall, I put in my vote in to continue in the RCC direction.  It is an excellent start.  I mean just look at how many use cases it covers.

Kevin
KevLinDev - http://www.kevlindev.com
Received on Friday, 18 July 2003 18:26:09 GMT

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