On Tue, Nov 29, 2011 at 10:04 AM, Chris Rossi <ch...@christophermrossi.com>wrote:
> On Tue, Nov 29, 2011 at 1:01 PM, Iain Duncan <iainduncanli...@gmail.com> > wrote: > > Hi folks, was interested in getting some subjective opinions on why one > > might use either FormEncode or Collander. We've been using formencode, so > > I'm curious as to motivations to switch and experience doing so. > > > > colander is actually a schema library used by deform, which is a form > library. You probably mean deform, not colander. I've worked on a > project that went from FormEncode to Formish, and have now worked on a > project that uses deform. The only thing I've been able to conclude > so far is I really don't like form libraries. That said, I'd probably > use deform now over formencode. But not for any reason I can > articulate at the moment. People seem to like flatland. I intend to > at least check it out at some point. > Actually I mean just the validation part. FormEncode IMHO is really a validation library, the form fill part is a tiny part of it. We have our own form generation ( well, actually multi view generation library ), but right now it uses FormEncode for validation and conversion. Thanks though! Iain -- 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.
