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: Thu, 26 Feb 2004 18:41:17 +0100
To: www-svg@w3.org
Cc: Cameron McCormack <cam-www-svg@aka.mcc.id.au>
Message-ID: <20040226174117.GA3096@linux>

Hi

On Fri 2004-02-27 Cameron McCormack wrote:
[...]
>   - A major change from the second release of the CSVG browser is
>   that the specification constraints is now backwards compatible
>   with standard SVG, so documents can be authored which will still
>   be displayed in standard SVG browsers. This example old CSVG code:
> 
>       <circle id="c" cx="100" cy="100" r="50"/>
>       <rect x="id('c')/@cx" y="id('c')/@cy" width="100" height="100"/>
>     
>     would now be written as this:
> 
>       <circle id="c" cx="100" cy="100" r="50"/>
>       <rect width="100" height="100">
>         <c:constraint attributeName="x" value="id('c')/@cx"/>
>         <c:constraint attributeName="y" value="id('c')/@cy"/>
>       </rect>

Is this valid? Do the SVG specs allow any elements from non-SVG
namespaces as content of rect? I didn't check the specs, and I think
the above makes sense, I'm just curious on what text you base your
assertion that the above is "standard SVG".

>   - Animation can be specified as expressions in terms of the time
>   since document load, returned by the CSVG function c:time().  For
>   example:
> 
>       <rect x="0" y="0" width="100" height="100">
>         <!-- move 20 units every second -->
>         <c:constraint attributeName="x" value="20 * c:time()"/>
>       </rect>

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.

>       <extensionDefs namespace="http://www.example.org/test">
>         <xsl:stylesheet id="xsl" version="1.1">
>           <xsl:template match="test:doubleCircle">

prefix "test" has not been declared, but it probably has been declared
outside the snippet I assume.

How did you implement the XSLT and XPath stuff; were you able to
leverage existing libs?

Tobi

-- 
Vim users, don't forget to
   http://iccf-holland.org/donate.html
Received on Thursday, 26 February 2004 12:34:55 GMT

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