On Mon, Apr 15, 2002 at 07:37:37PM +0200, Sven Kuenzler wrote:
> > > Anyway, would it really be too hard to make a SAXFilter that clones WW's
> > > core taglib functionality? Normally, the tricky part with SAX are state
> > > keeping issues. But most of this state keeping stuff should be handled
> by
> > > the ValueStack already. Or am I wrong?
> >
> > It's possible but not trivial -- tags that produce text are simle.
> > However, flow control and loop tags are tough because one must store the
> > events a "replay" them for every iteration.
>
> I see.
>
> > Aren't there any XML based
> > template engines out there?
>
> You mean, besides the dozens of XSLT engines? ;-)
> Well, there are:
> http://stx.sf.net/ Streaming Transformations for xml
> http://www.obqo.de/joost a STX implementation.
> Looks promising,. However, it's at a very eary stage.
>
> http://moe.sf.net/ Not template engine, but a "mixture" of event-based and
> tree-based XML processing. Alpha stage as well.
Where should we go then? IMHO a XSLT stylesheet with custom XSLT
extension should work well.
Stylesheet for the view could be
...
<xsl:template match="result">
<html>
<body>
...
<ww:value-of select="/ww-expr/goes/here" />
...
<ww:for-each select="/ww-expr/goes/here">
...
<ww:value-of select="." />
...
</ww:for-each>
</xsl:template>
Whereas the xslt engine uses custom handlers for the <ww:xxx> tags.
IIRC XSLT2.0 will specifiy a standard way to register XSLT extension.
-billy.
--
Meisterbohne Söflinger Straße 100 Tel: +49-731-399 499-0
eLösungen 89077 Ulm Fax: +49-731-399 499-9
_______________________________________________
Webwork-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webwork-user
