Re: Third release of Constraint SVG browser

Hi Tobias.

Tobias Reif:
> 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".

I think the others have covered this.

> 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?

> >       <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.

Yep.

> 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.  I needed to extend
it a bit to support treating attribute values as some typed object
rather than getting converted automatically to a string, but luckily
that wasn't too much work.  I managed to get away with just inheriting
from some of Xalan's classes rather than hacking the Xalan source (which
I did in the previous release).  The XPath classes had the ability to
register extension functions, so no extension of the XPath stuff was
needed at all.

Cameron

-- 
Cameron McCormack
|  Web: http://mcc.id.au/
|  ICQ: 26955922

Received on Thursday, 26 February 2004 18:29:12 UTC