[Catalyst] FormValidator::Simple Sillyness

Karl.Moens at marsh.com Karl.Moens at marsh.com
Wed Aug 30 10:02:02 CEST 2006

* Christopher H. Laco <claco at chrislaco.com> [2006-08-29 21:15]:
> So, imho, FV::S is not very object vs. class friendly. If I
> needed to set two different sets of messages for two seperate
> parts of an app that just happen to have the same action name
> (like save, load, delete, add, or anything else that is just
> descript), I'm screwed.
> This is even worse if you're running one process (Cat app) that
> hosts multiple sites within it, and each site might have it's
> own set of messages for form validation (aka, Mango).

I switched from HTML::Widget to CGI::FormBuilder as I found to have not
enough control over the the rendering of my forms in HTML::Widget.

CGI::FormBuiler plays very nice with Catalyst thanks to
Catalyst::Plugin::FormBuilder. If you take care to name your formfields the
same as your database columns, a simple "map" allows easy transfer from or
to the database. Your TT-templates can be as simple as
[%Catalyst.form.render%] if you accept the "standard layout" and all fields
have "class" and "ID" fields to be used with your CSS.

aka CountZero at Perlmonks

This message and any attachments are confidential. If you have received
this message in error please delete it from your system. If you require any
assistance please notify the sender. Thank You.

More information about the Catalyst mailing list