i agree with pretty much everything. the issues for me have been in separating the customization points for the right team members. my library just wraps validation & serialization by FormEncode, and helps automate the server side processing.
personally, i believe you should have form fields listed separately in the HTML templates and the setup/validation routines. i dislike automated form creation - i find the UX it creates to be very rough. On Tuesday, December 11, 2012 1:21:48 PM UTC-5, Arndt Droullier wrote: > > Forms have the nasty habit to connect to everything from css styling to > your data model and application logic. > And most libraries do this by defining their own scheme: > > - So the first thing you have to do is to write a wrapper and adapt the > form scheme to your application... > - Second: find the right places to customize the library, templates, > validators > - Third: if you need more than standard forms and still haven't quit -> > You end up with your own form library! > (and yes, I have one too) > > Honestly, I think the easiest and fastest way is to use a validation and > serialization library like colander to handle > the server side processing and manually build the form in html/ templates. > The good thing is you can > simply toss in any jquery form/input field modules and build the form just > the way you need it. > > Well, you will have the form fields listed twice, in the template and the > validation/serialization function, but > if you don't have too many forms this approach is still easier and faster > than handling a form library. > > Arndt. > > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/pylons-discuss/-/4YTjVYZtzhYJ. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
