On Friday 01 February 2002 02:08, Matt Sergeant wrote: > On Thu, 31 Jan 2002, Tod Harter wrote: > > Cool. We did find a few ways around some of the limitations in > > TaglibHelper as well, but your right, in general it is only good for > > fairly simple cases, more complex taglibs need something like what you're > > describing (which seems fairly close to the raw XSP interface). > > > > After looking at some other taglibs source code it seems to me that the > > XSP module itself could probably be enhanced via a few OO perl tricks so > > that you could just subclass it to create a taglib in a fairly clean way. > > In essence what it seems like to me is you want to maybe create a set of > > handlers that do the "compile time" part of the XSP automagically (so you > > just define methods like "parse_start_mytag($self,...)" and those just > > get called at the appropriate times. Should be pretty easy with an > > AUTOLOAD trick or maybe using some tieing tricks. > > See perldoc Apache::AxKit::Language::XSP. That's (almost) exactly how > "raw" taglibs work, except they're dispatched to different > modules/packages by namespace. For an example check out the ESQL taglib.
Honestly I'd just looked at the source of a few Taglibs. It looked like XSP just called "parse_start" and "parse_end" and you then had to build a test for what was being parsed. I'll have to dig down deep and check out how XSP actually dispatches that stuff. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
