On Fri, 7 Dec 2001, [iso-8859-15] J�rg Walter wrote:
> Hi!
>
> I've had some ideas about how to improve TaglibHelper. Currently, I dislike
> the way input and output is handled - there is no way to express certain XML
> structures, and for some input, information is lost. (see the TaglibHelper
> manpage, the person example:
> <friends><pid>3</pid><pid>5</pid><pid>13</pid></friends> is converted into
> friends => [ 3, 5, 13 ] - the sub doesn't know what name the inner tags had)
> Moreover, there is no real distinction beween attributes and content tags,
> which is bad, IMHO. So I developed a different TaglibHelper API, and the best
> part is: it can coexist with the current TaglibHelper in the same module.
> I think I will implement it for my own forthcoming taglibs, as it seems to me
> to be a natural way of doing things.
> My questions are: Is it really a good idea? Did I miss something? Is it
> useful to put it into the existing TaglibHelper? or even replace it somewhen?
> Why/When could the old TaglibHelper be better?
>
> Please CC me, since I don't want to join yet another mailing list.
Please do join the list - at any point in time I may close the list to
non-subscribers, which would make this impossible.
Anyway, I agree there's a problem, but I'm not entirely happy with the
solution... I think the hashed version of what gets sent isn't very nicely
structured - I'd much prefer something like the PerlDOM stuff Kip is
working on (is there a spec or design idea for that yet Kip?), so that we
can "plugin" some of the PerlDOM ideas like an XPath resolver, and just
have it magically work.
Plus I'm not convinced of the magic of start/end callbacks - should we
expect taglibs within taglibs to be called between those start/end
callbacks, and if so, what structure should they receive?
--
<Matt/>
/|| ** Founder and CTO ** ** http://axkit.com/ **
//|| ** AxKit.com Ltd ** ** XML Application Serving **
// || ** http://axkit.org ** ** XSLT, XPathScript, XSP **
// \\| // ** mod_perl news and resources: http://take23.org **
\\//
//\\
// \\
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
