I've just started digging into CGI::Application and thinking about how
to architect a small project of my own. Sorry if this is too basic,
but Google didn't help me and this thread may help others.
One question came to mind: I generally prefer to use one or two main
.shtml files to give a site
'
Subject: Re: [cgiapp] Using CGI::Application and SHTML/SSI pages?
Halley, Edward D. wrote:
I've just started digging into CGI::Application and thinking about how
to architect a small project of my own. Sorry if this is too basic,
but Google didn't help me and this thread may help others.
One
Halley, Edward D. wrote:
Thanks for the tips-- I'll look at Template Toolkit but I'm not
particularly fond of templates; it feels like the tail wagging the dog.
Really? I'm *so* glad that there are good templating solutions out
there. Separating the content from the code is a godsend. Being able
On Tue, Feb 22, 2005 at 02:13:04PM -0500, Halley, Edward D. wrote:
That's what CSS and the wrapping HTML are for. That's why an HTML
file which calls on one or more CGIs to render small, simply-
formatted lists is preferable (unless the server can't cope). In my
I don't want to engage in a
Brett Sanger wrote:
how do you pass parameters to an HTML page?
If you hit the URL http://foo/?bar=4baz=quux
and the index.shtml does !--include virtual=foo.cgi?$QUERY_STRING --
then the CGI parameters are passed as you'd expect. I would need to
check the exact SSI syntax when I get home, but
On Tue, 22 Feb 2005 14:13:04 -0500, Halley, Edward D.
[EMAIL PROTECTED] wrote:
Halley, Edward D. wrote:
Thanks for the tips-- I'll look at Template Toolkit but I'm not
particularly fond of templates; it feels like the tail wagging the dog.
Michael Peters wrote:
Really? I'm *so* glad
On Tue, Feb 22, 2005 at 02:41:27PM -0500, Halley, Edward D. wrote:
At this stage, I'm not committed to SSI, but it's more comfortable to
me than writing bottom-up by transforming templates into presentation.
I value others' impressions which have so far been offered.
Hi Ed,
At this point, I'm
Hi Edward,
Michael Peters has already given you a great answer that what you are
planning will work quite easily with CGI::Application. It will still
allow for a lot of code reuse, and if using mod_perl, you can still
benefit from DB handle caching and other benefits of mod_perl.
The only
At this stage, I'm not committed to SSI, but it's more comfortable to
me than writing bottom-up by transforming templates into presentation.
I value others' impressions which have so far been offered.
Ed,
I'm sympathetic to your position. I just came off two projects where I used
C::A
