As part of the Pylons-to-Pyramid howto I'm writing, I need to make
some recommendations for form handling. This covers the sprawling
topic of form generation, validation, error display, usage pattern in
the view, and side topics such as database records,
internationalization, and REST resources.
P
On 2011-1-17 20:23, Mike Orr wrote:
So, for those who've used them, is this true? Are they equivalent to
FormEncode, or are they missing any of FormEncode's functionality?
I have used formencode a lot in a Pylons 0.x context, and I've used a
lot of formish in repoze.bfg/Pyramid contexts. I hav
Hey Mike…
Am Freitag, den 14.01.2011, 19:53 -0800 schrieb Mike Orr:
> Hi all, I'm starting an article on Pyramid for Pylons 1 users,
> focusing on the differences between the frameworks and how to do
> familiar things in Pyramid. It'll also cover add-on stuff like forms
> and auth, or at least lis
Hello Mike,
On Mon, Jan 17, 2011 at 11:23 AM, Mike Orr wrote:
> So this email is to
> collect feedback for that: what are people using, and what do they
> think makes sense for Pyramid.
>
I'm still using formencode for validation/conversion. I use a custom class
that encapsulates the minimum f
Hello,
I am very interested in this topic since in my experience form
handling is always a pain.
Did you consider the "flatland" form processing package (http://
discorporate.us/projects/flatland/). I know this is a young project
but I think its a balanced compromise of schema creation, validation
