Hi John, "John C. Turnbull" <[EMAIL PROTECTED]> wrote on 08/26/2008 09:02:51 AM:
> Doing as you said does indeed stop the error but the script still > does not execute as intended. The stars that appear are supposed to > follow the path of the squiggle that is generated when you click the > mouse. Can you see any reason why this is not happening that way? Well there are two problems. The first is that Batik doesn't seem to pick up the change to the path on the animateMotion element after it has been added to the rendering tree. This can be worked around by simply moving the setAttribute call before the appendChild call in 'makeRun'. The second I'm honestly not sure if it's a Batik bug or a file bug. It has to do with the SMIL animation stacking. So we appear to apply the animateMotion and then we apply the animateTransform which I thought was correct but perhaps it's not. To be honest I'm not intimate with the animation stuff. > "John C. Turnbull" <[EMAIL PROTECTED]> wrote on 08/25/2008 08:24:21 AM: > > > I saw this SVG mentioned in a message to the SVG Developers list and > > tried it out with the latest build of Batik. It complains that the > > method cloneNode in AbstractNode does not exist. > > > > What does this mean exactly? > > It means that the JavaScript is trying to pass a string "true" > to a method that takes a boolean. If you change the call to > cloneNode so that it passes "true" without the quotes it seems to > work. > > > Is this a method that Batik is supposed to have implemented > > and/or is it something to do with the state of SMIL support in Batik? > > It's more of an artifact of how Batik's Java implementation of > the DOM interfaces with Rhino (the Java based JavaScript interpreter). > Since Java is strongly typed it tries to find a method that matches > the call from JavaScript. A native JavaScript implementation would > accept the string and since it isn't 'null' it would be treated as > passing 'true'.
