In this day and age, it amazes me that doing forms in web apps still sucks serious butt. Sure, we have HTML::FormFu, CGI::FormBuilder, HTML::Widget, Text::FormBuilder, FormValidator::Simple, and Data::FormValidator. They're all great at what they do, but they all suck in unique ways.
C::FB is great at form rendering, from a config file even, but it's validaton is lacking (and it only supports D::FV).
FV::S is great at validation, esp getting messages from config files, but getting profiles from config files is another story, and the YAML soon gets crazy.
D::FV is also a good validator, but I'm not terribly fond at how to get all of the errors our of results and setup custom messages...from config files is worse.
H::W make me feel ill every time I use it. All code, no external config. Easy to localize labels though.
FormFu looks promising, but at this point, I'm in crunch time, and it looks a little large for my needs. It's really good at localizaiton, even using the I18N plugin in Cat to do the job.
OF course, I could just hard code the forms, and just use FV::S, but doing the profiles in YAML is ugly as sin.
So, here it is, 2 weeks of form futzing with the various tools. In the end, just writing my own just to fill my needs seems like the only sane option so I can get back to actually getting work done. Plus, it gives me what I really wnat, a sane external config for form/validation/messages and even less code in most of my controllers.
- LENGTH, 1, 25
- LENGTH, 1, 100
A litte bit of FB. A little bit of FV::S. A little bit of D::FV. And no ugly nested nested arrays of lists. A little controller code to split that up into the various data bits for FB, D::FV and we're off to the races.