On 3/7/11 5:18 AM, Erez Schatz wrote:
IIRC, there were issues with labels on controls. We wanted no label on
a button, and had to override the button render method. There were
some other stuff in which the way we wanted the form to look didn't
fit the way H::FH thought a form should look, resulting in overriding
the rendering methods and lots of crufty code.
Setting the widget wrapper to 'None' for the form or the field, or the
'no_render_label' flag on a field, or setting the label in a field to ''
will all suppress rendering the label. Or you could use templates and
not use the rendering at all, or just render the bare input fields.
I'm not personally a fan of automatic rendering. It's pretty impossible
to come up with a standard way of rendering that everybody is going to
like, and adding tons of flags to handle every option is also a horrible
idea. Automatic rendering is good for prototyping, to make sure the
thing is working to start with. And it's good if you have a really
standard presentation where it's worth it to come up with a set of
widgets that fit your requirements.
Gerda
_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
