On Saturday 12 January 2002 18:32, you wrote:
> On Sat, 12 Jan 2002, Tod Harter wrote:
> > On Saturday 12 January 2002 02:54, you wrote:
> > > On Sat, 12 Jan 2002, Matt Sergeant wrote:
> > > > (Forwarding to the list)
> > > >
> > > > ---------- Forwarded message ----------
> > > > Date: Fri, 11 Jan 2002 17:20:05 -0800
> > > > From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> > > > To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> > > > Subject: returning a y:tag from x: taglib
> > > >
> > > > Hi,
> > > >
> > > > I would like to write a taglib that returns tags that require
> > > > evaluation from a different taglib. Particularly, I want
> > > > my taglib to return PerForm tags. How exactly would I do this ?
> > >
> > > For this to work you have to write your taglib as a SAX taglib, rather
> > > than using taglibhelper. It's a little more complex, but not
> > > showstoppingly so.
> > >
> > > The best thing I can do is point you to the ESQL taglib, which warp
> > > your fragile mind at first, but eventually you'll see that it calls the
> > > Util taglib for esql:get-xml
> > >
> > > :-)
> >
> > I would think this is the kind of application where you would want
> > "deeper" pipelines... In other words you could have 2 levels of XSP
> > processing, the first level can deal with taglib x, and the 2nd can deal
> > with taglib y. In many cases you can simply use 2 namespaces and combined
> > functionality of several taglibs, but there are cases like PerForm where
> > that may not be a good solution, so hence deeper pipelines, maybe even
> > something like XSP -> XSLT -> more XSP -> more XSLT...
>
> Ugh, SAX based is faster and cleaner. IMHO, of course. SAX based taglib
> combining is done in parallel, compiled, and just plain works. The code is
> simple. Really simple.
>
> XSLT is not simpler for developers. Thats the boat being missed here.
>
> my $el = { Name => "foo" };
> $self->start_element($el);
> ... # process blah
> $self->end_element($el);
>
> vs:
>
> <xsl:template name="...">
> ...
> </xsl:template>
>
> <xsl:template match="blah">
> <foo>
> <xsl:apply-templates name="..."/>
> </foo>
> </xsl:template>
Not sure I entirely agree with you on that one Matt. XSLT is declarative, and
thus a lot of people who are used to procedural programming aren't going to
like it much, but there is a HUGE amount of expressiveness possible in a
declarative syntax, if you can wrap your head around it. Once you do its good
stuff, as any LISP or Prolog guy can tell you. SAX is good for some things,
XSLT is good for others. The nice thing is that one can apply either tool
when its appropriate. The framework should make that as painless as possible.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
