Hey, guys, I wanted to say thanks for solving this issue. It's good to see that there was a solution that didn't involve a backwards-incompatible change.
On 11.08.2006 14:50:19 Cameron McCormack wrote: > Thomas DeWeese: > > [Cameron moves all of anim.jar into batik-svg-dom.jar] > > > > Oops, Sorry, this wasn't what I intended at all :/ > > Oh. :) > > > What I intended was that we move just > > AnimationTarget, AnimatableElement and AnimationTargetListener > > into the batik.dom package tree (forming "the new package"). > > Add the new package (containing just these three interfaces) > > to batik-svg-dom.jar and leave the rest of the code in the > > batik.anim package put in batik-anim.jar. > > Righto, done. > > > The bit about decoupling was really just pointing out that > > in theory one could use the SMIL engine for languages other > > than SVG (like people have used, or at least tried to use, > > the Batik CSS engine for languages other than SVG). > > Yes, I did think of this as I was writing it. There are really only a > few SVG specific classes in the anim.values package, shouldnt be too > hard. Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
