Aaron Trevena wrote:
On 24/02/06, Dave Howorth <[EMAIL PROTECTED]> wrote:
* Displaying hints for fields
- A required field should be marked as such in a form
That's a nice-to-have.
It would save hours - just being able to check if a field was required
or not, and updating the macros appropriately could save hours.
Yeah, I just meant that the form handling will pick up missing fields
and report errors after the event in any case, so marking them on the
blank form is not absolutely essential. But once you have a
required_columns array or somesuch it's easy to pass to the template.
Yes, I don't think there's any way I'll go back to CGI::Untaint.
I'd be happy to move to something else if we can provide backward compatibility.
I've no feel for how hard that would be. I think we'll be doing well if
we can come up with a system that most people can live with. Once that's
done, it'd be easier to see how hard a backwards compatibility layer is.
MyApp::Job->required_columns(qw/Title Salary FAO Closing_Date/);
That's pretty much the information in a DFV profile, in a slightly
different order.
See - above - I'd love to dump Untaint.
I'll be interested to see the interfaces in the form-handling stuff, to
see how hard it is to use a different implementation under them. At the
moment both my model and templates need to be custom.
Cheers, Dave
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Maypole-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/maypole-devel
