Jeremias Maerki:
> Just FYI:
> http://vmgump.apache.org/gump/public/xml-fop/xml-fop/index.html
> http://vmgump.apache.org/gump/public/xml-fop-maintenance/xml-fop-maintenance/index.html
> 
> I haven't looked into this more closely, yet.

Ah.  Taking a look at a couple of these:

  …/src/java/org/apache/fop/fo/extensions/svg/SVGElement.java:157:
  <anonymous org.apache.fop.fo.extensions.svg.SVGElement$1> is not
  abstract and does not override abstract method
  
removeTargetListener(java.lang.String,org.apache.batik.anim.AnimationTargetListener)
  in org.apache.batik.dom.svg.SVGContext

I extended SVGContext with a couple of methods that allow the animation
engine to listen to some events on an element.

  …/src/java/org/apache/fop/fo/extensions/svg/SVGElement.java:160:
  cannot access org.apache.batik.anim.AnimationTarget
  file org/apache/batik/anim/AnimationTarget.class not found
           ((SVGOMElement)e).setSVGContext(dc);

This is because SVGOMElement now implements the AnimationTarget
interface, and this interface is in the batik-anim.jar that is built.
Including it in the class path would solve most problems that arise.

I’ll investigate further this afternoon exactly what other things would
need changing from fop’s side.

Would it be helpful if I could rearrange some of the code so that for
static documents a dependency on the anim jar is not required?  I could
probably achieve this just by moving a couple of interfaces into one of
the other packages.  (Reducing the coupling here might be a good idea…)

-- 
Cameron McCormack, http://mcc.id.au/
        xmpp:[EMAIL PROTECTED]  ▪  ICQ 26955922  ▪  MSN [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to