On Thu, 8 Nov 2007, Kieren Diment wrote:
Good call, my mistake. Goes to show that there's not usually much (or any)
extra stuff that needs to be done in the View class. I was actually
struggling to think of code related things (rather than config) which you
might want to put in there. Pe
On 8 Nov 2007, at 16:16, Dave Rolsky wrote:
On Thu, 8 Nov 2007, Kieren Diment wrote:
TT.pm is the file that contains the programming logic for
rendering your view. You can do stuff like set http headers,
automatically add stuff to the stash/session/whatever and co in
here. It inherits
On Thu, 8 Nov 2007, Kieren Diment wrote:
TT.pm is the file that contains the programming logic for rendering your
view. You can do stuff like set http headers, automatically add stuff to the
stash/session/whatever and co in here. It inherits from Catalyst::View::TT
The View subclass for you
On 8 Nov 2007, at 15:59, Gerda Shank wrote:
I'm trying to learn Catalyst by working my way through the
tutorial and other docs, and I'm a little puzzled by the View
directory. In the tutorials it only has a TT.pm file in it, which
is a config file for Template Toolkit. Are there ever any
Gerda Shank wrote:
> I'm trying to learn Catalyst by working my way through the tutorial
> and other docs, and I'm a little puzzled by the View directory. In the
> tutorials it only has a TT.pm file in it, which is a config file for
> Template Toolkit. Are there ever any other kinds of files in th
I'm trying to learn Catalyst by working my way through the tutorial and
other docs, and I'm a little puzzled by the View directory. In the
tutorials it only has a TT.pm file in it, which is a config file for
Template Toolkit. Are there ever any other kinds of files in that
directory? The files
The way to do this would be to:
__PACKAGE__->config->{'Controller::FormBuilder'}->{new}={ debug=> 0};
Add this line to the controllers that use FormBuilder and it should
supress all form builder output
Balaji
On Nov 6, 2007, at 3:59 PM, Joe Landman wrote:
How do I selectively enable or disabl
Thanks for the links! Looks like Log4Perl does what I need. Wish I knew that
6 months ago... :-/
Karim Nassar
On 11/7/07, Jonathan Rockway <[EMAIL PROTECTED]> wrote:
>
> Karim Nassar wrote:
> > At my former employer, we had a logging infrastructure, but it had to
> > work with more than just cata
Karim Nassar wrote:
> At my former employer, we had a logging infrastructure, but it had to
> work with more than just catalyst, so it was not optimal.
I see what you're saying, but Catalyst can easily support custom
logging. You can make $c->log return whatever you want (see
Catalyst::Log::Log4p
If debugging via plugin is going to be added, it'd be super sweet if there
were support for full logging.
At my former employer, we had a logging infrastructure, but it had to work
with more than just catalyst, so it was not optimal.
I feel what is needed is the ability to log in any module such
J. Shirley wrote:
> On Nov 6, 2007 5:47 PM, Jonathan Rockway <[EMAIL PROTECTED]> wrote:
>
>> Joe Landman wrote:
>>> How do I selectively enable or disable debugging output?
>>> Specifically, FormBuilder debugging output is simply far to verbose to
>>> be meaningful to us. I suppose I could simply
11 matches
Mail list logo
