On Jan 11, 2004, at 10:22 PM, Peter Chen wrote:
On Jan 10, 2004, at 5:12 PM, John Lawton wrote:
If you want to trap templates you can match _tmpl.html instead.
C::A also has some design decisions that turn people off. (I like
C::A)
-john
You are missing my point.
To me, .html indicates
If you want to trap templates you can match _tmpl.html instead. C::A
also has some design decisions that turn people off. (I like C::A)
-john
On Jan 10, 2004, at 11:25 AM, Peter Chen wrote:
On Jan 7, 2004, at 11:23 AM, Mark Stosberg wrote:
I thought I would bring attention to CGI::Framework,
Another good question for best practices. With hierarchical organizing
schemes such as directories there will always be many different ways to
skin this cat. I have been avoiding this problem though I know that I
will soon have to come to terms with it. If you want to use a template
to
I see two potential problems in your code.
1. Do not use the redirect method of the CGI.pm object from withing
CGI::App to do a redirect. Use something similar to the code below.
$self-header_type( redirect );
$self-header_props( -uri = $redirect_url );
2. Be sure to indicate at least the
--- Mark Stosberg [EMAIL PROTECTED] wrote:
On Wed, 13 Nov 2002, Dirk [ISO-8859-1] Weßner wrote:
So far, so good. But what is the best practice to avoid writing
the code for populating TMPL_VARS in menu_bar.tmpl
in every run mode?
Yet another solution is to have all these run modes in a
