"Till, Jeff" <[EMAIL PROTECTED]> writes: > My company is considering switching from solely perl-based web > applications to perl applications supported with Template Toolkit. > What advantages does TT offer beyond what perl already provides? > For example, we already have functions in a perl library called > header() and footer() that will print out those components of the > pages. In short, do the advantages of Template Toolkit outweigh the > training and conversion time that would be needed to incorporate TT?
In my project, it helped a lot to separate presentation from logic: some people worked on presentation (implementing templates and documenting their parameters) while others developed the application logic. It worked (and works) very well. Among the others we get used to create sample parameters and generate static example pages from each template - and to discuss it with our client before implementing their logic. As I feel personally responsible for choosing TT for our project, let me also mention important reason which influenced this decision: TT allowed to break 'single request-single page' link which hurts a lot of web apps written in tools like ASP/PHP/JSP/similar. We are able to accept the request, process it (in perl) and then to choose which template should be applied and to which data. Really nice. -- ( Marcin Kasperski | If information is written down two ways, one of the ) ( http://www.mk.w.pl | versions will soon be out of date. (XP practices) ) (----------------------------------------------------------------------------) ( Nie gub zgłoszeń błędów: http://www.mk.w.pl/narzedzia/narzedzia_bugewid ) _______________________________________________ templates mailing list [EMAIL PROTECTED] http://lists.template-toolkit.org/mailman/listinfo/templates
