On Jun 21, 2010, at 10:18 AM, Kevin J. Smith wrote: > I would have to agree with Mike wholeheartedly. I think people's biggest > problem with FormEncode is they are not sure how to use it. I have > repeatedly heard people complain about the documentation but it actually > serves very well as reference but where it is lacking is in examples within > the web application context. It took me quite a bit of time to figure out > how to create custom validators and what not but once done, FormEncode has > been a pretty valuable asset. > > The problem with the validation wrapper is that it is not very flexible and > it was designed for a very narrow use case.
Also, there's the rather good, and FormEncode/formish inspired libraries, Colander and Deform: http://docs.repoze.org/deform/ http://docs.repoze.org/colander/ Though they both still setup a class for the form. This generally makes sense for organization purposes, I wouldn't call organizing a batch of validation settings into a class 'MVC', its just an organization scheme. Cheers, Ben -- 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.
