RE: [Catalyst] C::C::FormBuilder question

2007-01-31 Thread Marc Logghe
-Original Message- From: Juan Camacho [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 30, 2007 6:22 PM To: The elegant MVC web framework Subject: Re: [Catalyst] C::C::FormBuilder question On 1/29/07, Marc Logghe [EMAIL PROTECTED] wrote: Actually, the docs give a TT example:

Re: [Catalyst] C::C::FormBuilder question

2007-01-31 Thread Carl Franks
On 30/01/07, Matt S Trout [EMAIL PROTECTED] wrote: On 30 Jan 2007, at 08:48, Carl Franks wrote: I was just looking at this last week, as I was using the code as a basis for a new controller. I suspect that it's never been tested, because as far as I can tell, it incorrectly reads the config

Re: [Catalyst] Hair-pulling over YAML config

2007-01-31 Thread Chisel Wright
On Tue, Jan 30, 2007 at 12:11:22PM -0600, Jonathan Rockway wrote: To be read from the unparsable/invalild config file? ;-) If the config file was parsed OK there's no need to report errors. Because there weren't any. /me heads off to drop a cat with a buttered slice of toast tied to its

Re: [Catalyst] Hair-pulling over YAML config

2007-01-31 Thread David Morel
Le 30 janv. 07 à 19:11, Jonathan Rockway a écrit : Chisel Wright wrote: On Tue, Jan 30, 2007 at 09:58:00AM -, Carl Vincent wrote: That's exactly what we need - outputting warnings at on of the ConfigLoader levels loses the content of the error message. Could always add a Keep Quiet

Re: [Catalyst] Hair-pulling over YAML config

2007-01-31 Thread leonard . a . jaffe
On Wednesday 01/31/2007 04:42 AM, Chisel Wright wrote: /me heads off to drop a cat with a buttered slice of toast tied to its back ... Feet. Buttered toast tied to its feet. l. -- Leonard A. Jaffe - This transmission may contain information that is

Re: [Catalyst] Hair-pulling over YAML config

2007-01-31 Thread Matt S Trout
On 31 Jan 2007, at 14:49, [EMAIL PROTECTED] wrote: On Wednesday 01/31/2007 04:42 AM, Chisel Wright wrote: /me heads off to drop a cat with a buttered slice of toast tied to its back ... Feet. Buttered toast tied to its feet. Depends which way up the toast is. -- Matt S Trout,

Re: [Catalyst] Accessing $c from Model

2007-01-31 Thread Juan Miguel Paredes
On 12/27/06, Ash Berlin [EMAIL PROTECTED] wrote: Mark Zealey wrote: Hi there, I'm basically wanting to write a simple log function which logs hits on my website as entries in a database (automatically adding $c-user-{id} and $c-req-referrer etc), but to do so I want to use a model (I

Re: [Catalyst] Hair-pulling over YAML config

2007-01-31 Thread Jonathan Rockway
Chisel Wright wrote: /me heads off to drop a cat with a buttered slice of toast tied to its back ... I tried this this morning. The cat won. -- package JAPH;use Catalyst qw/-Debug/;($;=JAPH)-config(name = do { $,.=reverse qw[Jonathan tsu rehton lre rekca Rockway][$_].[split //, ;$;]-[$_].q;

Re: [Catalyst] Accessing $c from Model

2007-01-31 Thread Matt S Trout
On 31 Jan 2007, at 15:23, Juan Miguel Paredes wrote: On 12/27/06, Ash Berlin [EMAIL PROTECTED] wrote: Mark Zealey wrote: Hi there, I'm basically wanting to write a simple log function which logs hits on my website as entries in a database (automatically adding $c-user- {id} and

Re: [Catalyst] Accessing $c from Model

2007-01-31 Thread Juan Miguel Paredes
On 1/31/07, Matt S Trout [EMAIL PROTECTED] wrote: On 31 Jan 2007, at 15:23, Juan Miguel Paredes wrote: Hi, all! What if we have to overload ACCEPT_CONTEXT to do something like this, but using DBIC::Schema? What would be the recommended inheritance chain? Catalyst::Model::DBIC::Schema

[Catalyst] FormBuilder + C::C::Formbuilder memory leak fixes

2007-01-31 Thread Victor Igumnov
To see the impact of the memory leak. Run broken.pl first which will run formbuilder against your installed version. It will create a new formbuilder instance over and over, watch top -o size as it grows to 100-200 megs in just a few seconds. Now run fixed.pl - works great don't it? No

Re: [Catalyst] FormBuilder + C::C::Formbuilder memory leak fixes

2007-01-31 Thread Juan Camacho
On 1/31/07, Victor Igumnov [EMAIL PROTECTED] wrote: To see the impact of the memory leak. Run broken.pl first which will run formbuilder against your installed version. It will create a new formbuilder instance over and over, watch top -o size as it grows to 100-200 megs in just a few