> We will implement that when we implement SMIL. Batik does not support
> SMIL yet, so there is no point in ElementTimeControl yet, even though
> I hope we will get to it soon (current plan is after the final 1.5
> release).

Makes sense.  Having played with XSmiles though, I am starting to wonder 
about the roles of the different toolkits.  Near as I can tell, in large 
part the Batik and XSmiles projects will continue to converge in terms of 
feature sets.  They will likely never meet (I can't see Batik doing XHTML)
  but they will get close (my bet is that Batik will implement XForms 
sometime soon-ish).  I guess what I'm saying is that both products look 
like they could learn from and work well together.

Even if that doesn't turn out to be the case, it does beg the question as 
to how a third-party developer would use Batik to add SVG capabilities to 
their application?  For basic viewing it looks straightforward.  What I'm 
wondering is how I would go about wiring in an XForms implementation, or 
some other scriptable <foreignElement>?  I get the impression from the 
XSmiles mailing list that it's those interactions that are the real trick.
   Now that the W3 is releasing composite document specifications ("An XHTML 
+ MathML + SVG Profile") the ability to easily hook the scripting and DOM 
features together may become really important.  This is what led to me to 
the question about the BSF.

Personally I'd love to see Batik and XSmiles integrated into each other, 
especially if that work provides a model for hooking other <foreignObjects>
  together to support multi-namespaced documents.  Unfortunately my 
programming skills are not up to the task.

> We do not have any plan to use BSF. Note that you can use Batik with
> JPython (see http://xml.apache.org/batik/scripting.html and the
> org.apache.batik.script.jpython package). The doc is very short but
> tells you that using JPyhon is possible and we actually have an
> implementation.

Thanks for pointer.  Out of curiosity, why is moving to BSF not part of the 
plan?  My guess is that it's because Batik needs access to scripting 
language features that are more "concrete" than the abstraction presented 
by the BSF.

Thanks for your insights.

Jason Foster


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

Reply via email to