Matt,
I think you might want to look at CGI::FormBuilder, a library that builds
the same sort of construct you describe. It doesn't use Mason, but there is
no reason you cannot use the library from within Mason components. It might
make your life easier.
Personally, I never put complex data valid
Matt Warnock wrote:
Mason newbie, so please be kind.
Not a chance ;)
I like having a web form and its associated error-checking in the same
file. Makes it easier if I have to make a design change later. So I
thought I'd have the form component call itself as its form action.
If in th
> All the functions related to that record type in
> one file. Is this a bad idea? How do Mason experts do this?
It doesn't sound like a bad idea. I used to do it that way. (Now I
use a lot of AJAX calls).
>
>
> However, it would be nice to be able to bail out of the <%init>
> section
> ea
Mason newbie, so please be kind.
I like having a web form and its associated error-checking in the same
file. Makes it easier if I have to make a design change later. So I
thought I'd have the form component call itself as its form action.
If in the <%init> section, the $ARGS{submit} value is
4 matches
Mail list logo
