in reply to Re: Re: Re: Template Toolkit and XML
in thread Template Toolkit and XML

Well, that looks like two votes from you guys, and I definately will change that now. My original plan was to parse "X" keys out, and just dump that to the screen... as you both pointed out, that's misguided. So it seems my idea of "one place" is out of line, I'll change this to throw the variables into TT (which I'll be back tomorrow probably ;)

It just seemed logical to me to separate the data and presentation layers, but now it seems I have two "middlemen", if you will... one .pl to parse the document, and one to present it -- on top of the data layer. I'm actually wondering why I can't just do this in XSL/T (which it seems pretty much what this module is doing) and drop it in that way. The one who suggested it happens to be the boss, and he's not up on Perl/TT that much either. Luckily, he's the type that should listen to reason.

--DesertGhost

Thanks to you both... I'll get on this tomorrow and see if that's a bit easier.

  • Comment on Re: Re: Re: Re: Template Toolkit and XML

Replies are listed 'Best First'.
Re: Re: Re: Re: Re: Template Toolkit and XML
by perrin (Chancellor) on Apr 21, 2004 at 04:56 UTC
    It just seemed logical to me to separate the data and presentation layers

    Right, which is exactly what you are not doing by making your template parse the data and decide what to display.

    I'm actually wondering why I can't just do this in XSL/T

    You probably can. Go for it, if you like XSLT. XML::LibXML is still probably your best bet for that.