Yeah, except that if you are using C::A::Plugin::ValidateRM you won't need the error_form, because the DFV plugin will refill your original form, and if you have your templates set up right, it will add error messages if any fields failed to validate.
Barry -----Original Message----- From: Ski Kacoroski [mailto:[EMAIL PROTECTED] Sent: Thursday, September 15, 2005 11:46 AM To: Michael Peters; [email protected] Subject: Re: [cgiapp] Is there a better C::A design pattern > I'd look into Data::FormValidator for that kinda validation. In > particular C::A::Plugin::ValidateRM is pretty handy. > I saw it last night, did not have time to check it out in detail. > > > I usually split the display of a page and the processing of that page's > data into 2 separate run modes. Others keep them in the same one. I like > the first approach because the 2nd reminds me too much of PHP :) > So you run something like this: runmodes { display_start_form, process_start_form, display_next_form, process_next_form, } Then in the display_start_form set rm = process_start_form and in process_start_form call either an error_form or display_next_form? cheers, ski -- "When we try to pick out anything by itself, we find it connected to the entire universe" John Muir Chris "Ski" Kacoroski, [EMAIL PROTECTED], 425-681-0092 --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
