Re: [cgiapp] Good practices: how many run modes in an app

2005-12-18 Thread Jeff MacDonald
Jesse, Af few weeks ago, I asked a question about a snazzy way to do a fill in form in one line return $self-fill_form($self-tt_process({}),$self-dbh-selectrow_hashref(SELECT * from menus WHERE id = ?,{},$id)); Since this uses dbh directly, in Krang to do something similar does that mean you

Re: [cgiapp] Good practices: how many run modes in an app

2005-12-18 Thread Ron Savage
On Sun, 18 Dec 2005 09:19:18 -0500, Cees Hek wrote: Hi Cees That is the rule I follow as well. The only time the CGI::App Same here. object sees a DBI handle is when it needs to pass one to a plugin (like the session plugin). It never ever uses it directly. Right. -- Cheers Ron Savage,

[cgiapp] Good practices: how many run modes in an app

2005-12-17 Thread Brad Cathey
I'm writing a medium-sized web-based financial application that will have up to 50 run modes between presenting empty forms, saving, editing, updating, and deleting from them. Run modes *could* be broken down into groups, e.g., these 4 deal with managing users, these 6 deal with managing project

Re: [cgiapp] Good practices: how many run modes in an app

2005-12-17 Thread Michael Peters
Brad Cathey wrote: I'm writing a medium-sized web-based financial application that will have up to 50 run modes between presenting empty forms, saving, editing, updating, and deleting from them. Run modes *could* be broken down into groups, e.g., these 4 deal with managing users, these 6

Re: [cgiapp] Good practices: how many run modes in an app

2005-12-17 Thread Brad Cathey
Thank you Michael, that was very helpful. Unfortunately it uncovered areas I'm unfamiliar with, that a good study of OO will help. Brad Cathey wrote: I'm writing a medium-sized web-based financial application that will have up to 50 run modes between presenting empty forms, saving, editing,

Re: [cgiapp] Good practices: how many run modes in an app

2005-12-17 Thread Rob Kinyon
On 12/17/05, Brad Cathey [EMAIL PROTECTED] wrote: I'm writing a medium-sized web-based financial application that will have up to 50 run modes between presenting empty forms, saving, editing, updating, and deleting from them. Run modes *could* be broken down into groups, e.g., these 4 deal