Hi Cameron,
Cameron McCormack <[EMAIL PROTECTED]> wrote on 08/11/2006 01:08:46 AM:
> Thomas DeWeese:
> > For everyone's convenience I would even lean towards just adding
the
> > new package to the list of packages included in batik-svg-dom.jar
during
> > the jar file build. If someone requests that we decouple the
animation
> > engine completely we can do that later.
>
> Ok I have done this.
[Cameron moves all of anim.jar into batik-svg-dom.jar]
Oops, Sorry, this wasn't what I intended at all :/
Cameron McCormack <[EMAIL PROTECTED]> wrote on 08/10/2006 03:36:30 AM:
> A solution would be to have two jars: one (anim-intf.jar) that
> contains these interfaces (AnimationTarget, AnimatableElement
> and AnimationTargetListener) and another (anim.jar) that
> contains the rest of the anim package.
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.
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).
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
