Re: 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, kacoroski@xxxxxxxxxxx, 425-681-0092

---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/cgiapp@xxxxxxxxxxxxxxxxx/
             http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: cgiapp-unsubscribe@xxxxxxxxxxxxxxxxx
For additional commands, e-mail: cgiapp-help@xxxxxxxxxxxxxxxxx