Re: [cgiapp] CAF methodology

2006-11-11 Thread Aleksandar Petrovic
Because the things like those plugins I switched to TT (used HT before). With TT it's much easier to do things like that - especialy if you need to pass some parameters to your plugin. Say an online visitors counter - but in one place you wan't to display also the last 5 visitors (last 5

RE: [cgiapp] CAF methodology

2006-11-10 Thread Dan Horne
Yep - see CGI:Application::Plugin::AnyTemplate - Dan -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Robert Hicks Sent: Saturday, 11 November 2006 3:15 a.m. To: cgiapp@lists.erlbaum.net Subject: [cgiapp] CAF methodology CGI::Application::Framework has an idea

Re: [cgiapp] CAF methodology

2006-11-10 Thread Mike Friedman
With Template Toolkit, if you pass your $self object to the template, then you can just say: [% self.some_other_run_mode %] Though if I wanted to embed runmode output, I'd probably just pass it to the template as regular data. my $output = $self-some_other_run_mode; $self-tt_process( {

Re: [cgiapp] CAF methodology

2006-11-10 Thread Cees Hek
On 11/10/06, Mike Friedman [EMAIL PROTECTED] wrote: With Template Toolkit, if you pass your $self object to the template, then you can just say: [% self.some_other_run_mode %] And if you use the CAP::TT plugin, that is automatically done for you, except the variable is called 'c'. [%

Re: [cgiapp] CAF methodology

2006-11-10 Thread Sam Tregar
On Fri, 10 Nov 2006, Robert Hicks wrote: I think that is a pretty cool idea and was wondering if anyone likes that as well. Is there a plugin for it or anything (outside of CAF)? Seems a little silly to use a plugin for: $template-param(foo_mode = $self-foo); And: tmpl_var foo_mode If