> : Well, I'm really hoping to make TT a Mason-killer. :) > > I agree! You can do a lot of cool things with Apache::Template that > make it much easier to use. You can even install your own service > modules to do a bunch of data munging before the template pages are > processed. Apache::Template is just about there in terms of a > Mason-killer.
TMTOWTDI. My feeling is that TT is the best available solution for doing model-view-controller apps with real separation of application logic and display logic. On the other hand, if I were doing something with in-line Perl or a similar callback approach, I would probably use Mason or Apache::ASP. I'm not eager to make TT all things to all people. In my view, Apache::Template fosters bad habits because it makes it more difficult to keep your application logic separate. If the service stuff was expanded to provide something along the lines of the (Java) Struts project (i.e. config-based mapping of a URI to a module which runs some application logic and then selects a template for the view), that would be cool. Right now it maps URIs directly to template files, which is usually not good for applications doing anything fancier than SSI-ish templating. (Sure, you can subclass it and change all of this, but newbies aren't going to grasp that easily.) - Perrin
