in reply to Re: Re: Re: Three-layer web application architecture
in thread Three-layer web application architecture

TT is practically a full-fledged language of its own

I consider that the downside of TT. Look at some of the awful things people do with it when they try to do complex things in the template. Apache::Template is commonly a source of great evil. However, I think the majority of users are still treating it as a simple display-oriented language.

  • Comment on Re: Re: Re: Re: Three-layer web application architecture

Replies are listed 'Best First'.
Re^5: Three-layer web application architecture
by adrianh (Chancellor) on Nov 17, 2003 at 18:10 UTC

    I've also seen people do truly awful things with HTML::Template. Because of the lack of expressive power in the templating language "view" related code migrates back into the controller/model, making it a complete pain to change the layout.

    What it comes down to (as always :-) is getting vaguely bright people to do the project who understand how to separate concerns, and then using whatever tool does the job best - be it HTML::Template, Template Toolkit or whatever.

    (I do agree about the evil people do with Apache::Template tho' :-)

Apache::Template considered harmful!
by cleverett (Friar) on Nov 17, 2003 at 22:06 UTC
    perrin sez:

    Apache::Template is commonly a source of great evil. However, I think the majority of users are still treating it as a simple display-oriented language.

    Permit me to rephrase that: Apache::Template makes it damned hard to do anything other than display data. Which means that cruft sets in as soon as one tries to do more.

    perrin's advice saved me from going down that path some time ago.