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

Re: Third release of Constraint SVG browser

From: Tobias Reif <tobiasreif@pinkjuice.com>
Date: Fri, 27 Feb 2004 10:46:56 +0100
To: www-svg@w3.org
Cc: Cameron McCormack <cam-www-svg@aka.mcc.id.au>
Message-ID: <20040227094656.GA3315@linux>

Hi Cameron

On Fri 2004-02-27 Cameron McCormack wrote:
> > The advantage of declarative animation statements (such as
> > SMIL/SVG) is that the motion's resolution (eg fps) is not set in
> > stone and can thus be adapted and optimized. The same animation
> > can be performed with 50 fps on a fast machine, with 10 fps on a
> > tiny phone, or with "perfect resolution" by a robot.
> Why would this not be the case for animations written in terms of
> some function?

It is not the case for your code I commented on:

<rect x="0" y="0" width="100" height="100">
  <!-- move 20 units every second -->
  <c:constraint attributeName="x" value="20 * c:time()"/>

As your inline comment correctly states the resolution (fps) is set in

"Some function" or some code definitely can animate something in a way
that the animation will run in different resolutions depending on
various (environment) parameters, or even without a fixed fps rate =
variable frame pauses. For example: Check the current real time, check
where the object should be next (eg a percentage of the specified
duration and distance), then move it there; after this has been
finished start with the next iteration. The frame pause can vary each
time depending on how long it took the machine to calculate and render
the last frame.

> > How did you implement the XSLT and XPath stuff; were you able to
> > leverage existing libs?
> Yes, I pretty much just dropped in Apache's Xalan.

Great! When you want to try XSLT 2.0 you could see if you can use
parts of Saxon.


Vim users, don't forget to
Received on Friday, 27 February 2004 04:46:59 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:46:58 UTC