> On Mon, Jan 23, 2012 at 8:00 AM, BruceC <[email protected]> wrote: > > To my mind there are 2 possible approaches here: > > 1. Modify pyramid_simpleform so that it can use a schema generated by > > Colander rather than FormEncode (and in a perfect world, be able to > > define form widgets in that schema as well) > > 2. Modify Deform so that it provides pyramid_simpleform-type methods > > for rendering the individual parts of a form in a template. > > > > My personal preference would be for the latter. I like Deform & > > Colander. I like being able to define a form schema that specifies the > > widget & the validation all in the one place. If you have an > > enterprise app with over a hundred forms, things can get messy pretty > > quickly :) > > > > Anyone have any tips on where you might start looking at modifying > > Deform to allow it to render specific form parts? > > > > -BruceC
I think you can style the form quite to your liking by replacing the "form" and "mapping_item" templates. However deform uses an ordered sequence of form fields to validate and process form data. You have to maintain this order or the whole form won't work. (At least I ran into this problem several times.) My impression is deform has too many advanced features to make form handling really 'easy'. Or? Arndt. -- 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.
