W3C home > Mailing lists > Public > www-svg@w3.org > March 2004

Re: SVG 1.2 - 3.2.1 editable

From: Peter Sorotokin <psorotok@adobe.com>
Date: Mon, 22 Mar 2004 07:53:57 -0800
To: Cameron McCormack <cam-www-svg@aka.mcc.id.au>, www-svg@w3.org
Message-id: <5.2.0.9.2.20040322074726.01fafc58@mailsj-v1.corp.adobe.com>

I thought about this approach and I think it is not going to work. The 
current model is that everything is in the DOM. Basically, there is no 
"hidden state" in SVG; the only such state is SMIL animation resolved time 
(things like foo.click resolved to actual clock time of the click). If we 
are to go with the model that allows one to change animated values 
arbitrarily, we'd have to agree that every element potentially holds hidden 
animated state. This is a fairly different model - and it has big 
implications for many useful optimizations.

Peter

At 11:51 PM 3/22/2004 +1100, Cameron McCormack wrote:

>Chris Lilley:
> > If it doesn't work in the presence of animations then I don't see the
> > point.
>
>My point is for simulating the effects of animation.  If I want to
>provide animation-like features it would be nice if I could do so while
>retaining the base value.
>
> > Your proposal (change the animated value in script) and the current
> > method (change the baseval in script) are the same, if no animation is
> > running; the current method continues to work correctly if an
> > animation is running.
>
>Except that the base value is permanently overwritten.  Other script
>in the document (which may not be written by me) may want access to the
>base value as well as the (simulated) animated value.
>
>--
>Cameron McCormack
>|  Web: http://mcc.id.au/
>|  ICQ: 26955922
Received on Monday, 22 March 2004 10:59:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 5 November 2012 23:52:55 GMT