personally, think it would be best to decouple the moving parts as
much as possible
to me, there is :
html form creation - great if this is baked-in, but it shouldn't be
required
form validation - i think formencode is fine, but i often use it as
a first-pass and then handle things in my
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.
FormEncode allows me to build forms right from the schema. At this
point, if you need something like a GridTable layout, FormEncode is
the only solution I've found.
I moved from Formish to Deform and I find Deform to be quite powerful
and quite good, though I hate the li form aspect and much
I would like to suggest a tutorial on using Deform. I am experimenting
on it, and find it is not too difficult to learn. As a novice and not
actually a 'fulltime programmer', I found out that its integration with
pyramid is quite easy. I am trying to use pyramid_formish, but still can
make