The reason I was trying to stick with A::T is that others will be managing the site day to day and I want them to be able to change the configuration without looking at Perl code. So easy for me is not easy for them.
I'm using the 2nd approach to setup a user information object for the template. I'll think about putting the other functions in there. It certainly would make param handling easier.
I like dynamically choosing the template but I guess dynamically including components will do the same.
You're right to point out that it's starting to get messy though.
In reply to Re: Re: Calling Apache::Template's handler directly
by bsb
in thread Calling Apache::Template's handler directly
by bsb
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |