On Monday 25 November 2002 09:18 am, Robin Berjon wrote: > Matt Sergeant wrote: > > On Saturday, Nov 23, 2002, at 14:48 Europe/London, Tod Harter wrote: > > It's not bad per-se. It's just a bad idea to try and rip out our > > excellent implementation of XSP (arguably better designed than Cocoons - > > even most of the Cocoon developers agree with me on this) and replace it > > with something unknown, and in the meantime break both SimpleTaglib and > > TaglibHelper, which only work *because* of our current design. > > No one proposed that, I know I certainly didn't. I'm just considering the > option that using XSLT (and not in the way that Cocoon does it) *may* be an > interesting approach. No one is saying that AxKit 1.7 should ditch its XSP > implementation, we're just discussing alternatives that could be cool (and > perhaps eventually better -- you never know). > > We're hackers, we want to play!
Yeah, I agree with Robin, and it doesn't HAVE to be called "XSP" (though I would like it to be syntactically identical to XSP at the page level unless someone has a better idea) Heck, what about allowing 'XSLT sections" in XSP? In effect letting you directly include a template into your xSP. For certain lightweight tasks that might actually make sense... Or maybe its a dumb idea, but I find that the only way to find out what makes sense is to try it, since you usually find some completely unexpected use for a new capability. -- Tod Harter Giant Electronic Brain --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
