Re: Re: Calling Apache::Template's handler directly

Thanks.

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.

Comment on Re: Re: Calling Apache::Template's handler directly

Replies are listed 'Best First'.
Re: Re: Re: Calling Apache::Template's handler directly by perrin (Chancellor) on Jan 06, 2003 at 05:27 UTC
You could actually keep the config inside httpd.conf but do it with PerlSetVar commands that you read in your code. I can't tell exactly what you're doing with the user information object, but the approach I was referring to uses the TT2ServiceModule option. You might want to take a look if that's not what you're doing now. I completely agree that running some code and then dynamically choosing a template is better, which is why I don't use Apache::Template. It's much easier to do that when you call Template directly.	[reply]

Replies are listed 'Best First'.

Re: Re: Re: Calling Apache::Template's handler directly
by perrin (Chancellor) on Jan 06, 2003 at 05:27 UTC

I can't tell exactly what you're doing with the user information object, but the approach I was referring to uses the TT2ServiceModule option. You might want to take a look if that's not what you're doing now.

I completely agree that running some code and then dynamically choosing a template is better, which is why I don't use Apache::Template. It's much easier to do that when you call Template directly.

[reply]