Hola, I've been using deform and colander to render forms for internal apps here at work for the past couple of years. It works just fine for the utility apps I've been doing in-house. The pre-registration form I'm pulling together has about 40 fields that I want to break up into 6 sections. I'm thinking I want to group the fields in fieldsets, although idea is half-baked at the moment.
I really dig all the deform widget magic and building custom colander validators is pretty simple. Although the deform-rendered forms are simple and functional, they're also kind of horse-faced by default (apologies to any horses out there.) While it's been fine for our internal applications, these apps I'm working on now are going to be public-facing, and I know I'm going to need a bit more control of the layout. I keep getting pulled into project management stuff, and I'm lucky these days if I get to code for any length of time. If someone has examples of how I might get better renders via deform, or maybe some example of using some hand-built forms but still use the deform/colander validation and error responses, or an entirely different approach that I should be using instead, I'd be grateful. I'm open to just about anything at this point. Lurking on this list the past few years, I really appreciate your ideas or opinions. Thanks, Kurt -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
