On Dec 13, 11:45 pm, Mike Orr <sluggos...@gmail.com> wrote: > If you have specific questions about which libraries to use on top of > Pyramid, such as which form library to choose, describe what kind of > form API or "workflow" you expect, and we can suggest something the > most similar. Do you just want a quick-and-easy form based on an > object-oriented model? Do you want to control precisely how the form > looks? Do you require Javascript, or do you have external Javascript > you want to integrate? All these point to a different subset of form > libraries. >
Nice posting there. As for the forms, you're right, I'd like them to be pre-generated based on the model, with the ability to pull validation constraints from it, and fill the form errors in case of constraint violations. Both at the field-level, and at the overall form-level, detecting arbitrary cross-field inconsistencies based on custom validation defs. Just how Django does with its ModelForm. Of course adding any extra custom fields should be possible, too. And it would be perfect if the basic constraint checking (like min/max, non- empty, etc.) were duplicated in the client-side JS code, to save a round-trip to the server. The whole idea is to stick to the DRY principle - keep data in one place. The model's data options should be all that is necessary to present a form, validate it, and store the data. Plus any custom validation defs, of course. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. 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.
