David Cross <[EMAIL PROTECTED]> writes:
> From: Piers Cawley [mailto:[EMAIL PROTECTED]]
> Sent: 27 November 2000 10:27
> >
> > Dave Cross <[EMAIL PROTECTED]> writes:
> > >
> > > What happened to:
> > >
> > > thou shalt use CGI.pm
> >
> > Because CGI.pm is a bloated overweight piece of crap that breaks the
> > 'thou shalt not mix code and html...' guideline big up massive stylee,
> > and has some more than a little scary action at a distance stuff going
> > on with it.
>
> All true, of course, I wonder what happened to Schwern's[1] plan to produce a
> number of cut down CGI modules.
>
> For TT-driven CGI scripts, I find myself doing
>
> use CGI (:cgi);
>
> a lot. Because that's really all that _should_ be in CGI.pm.
Eww. I do all that stuff in my controller modules. The template gets
passed a 'param' object that got generated by the controller module
which had access to the Apache request object and a couple of other
bits of stuff. The templates themselves just mess with that. (And not
just because typing 'param.foo' is quicker that typing
'r.param("foo")', but because it means that I can test the templates
without having to muck about with LWP or setting up
Apache::FakeRequests.
--
Piers
