Jason,
Jason Foster wrote:
>
> > 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.
>
You are very right and we are actually going to work together.
Kari, one of the SMIL implementors in XSmiles recently joined the
Batik contributors and we will work 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.
>
This is very interesting and it would be interesting to have other
opinions on the issue. I personnally think that integration of SVG
and XForms is a *great* idea.
> > 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?
I think that there was a license issue when we looked at it initially
(that was a year and a half ago). I have not looked at the license
terms recently, so it may be less problematic now. I also think
remembering
some reluctance to add another 3rd party jar file...
Personnally, I'd be open to it if there is a good reason for making the
switch and it adds value people want. But I do not think we have anybody
who
would work on this right now (but a new contribution is always possible
:-).
May be the other commiters can comment on what they recall on that
topic.
Vincent.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
