Michael, I wonder if you might give an idea of how you handle that? Do you manually put forms into templates and validate yourself, or do you still use a validation library but with custom templates. Just wondering as I have tried both before.
Ben On 13 December 2011 15:48, Michael Bayer <[email protected]> wrote: > > On Dec 13, 2011, at 6:09 AM, Chris McDonough wrote: > > On Tue, 2011-12-13 at 01:59 -0800, rihad wrote: > > > > You are presuming that there is a one true form library that does > everything well that is completely satisfactory in all cases. I can > tell you from pretty hard experience that this is not true. To the > extent that I recommend a single form library, I tend to recommend > Deform because a) I wrote it and b) it's a Pylons project. But I always > qualify my recommendation of it with "it's great for autogenerating > forms, but it's not so great if you want pixel-control over the layout". > For that, I tend to recommend pyramid_simpleform (also a Pylons > project). > > > Plus, I despise autogeneration of form HTML - it's not compatible with the > organizations I work in, where layout is hand-designed by client side > developers. What works for some kinds of organizations doesn't work for > others. > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/pylons-discuss?hl=en. > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
