On 1/22/12 7:54 PM, BruceC wrote:
Deform& Colandar is fantastic if you don't care how your form is
displayed in layout terms, but if you need to specify layout, there is
no clear way to do that. For some of us, that is the crucial
difference determining which forms framework to adopt. If deform had
some simpleform-type form field rendering methods - eg $
{ myform.field('foo').label() }, ${ myform.field('foo').value() }& $
{ myform.field('foo').errors() } - that would definitely make it a
more broadly functional package imho...
FWIW I'm using deform for fun & profit and would like to see this too.
Maybe mcdonc could lay out a way for us to get there, assuming someone
wants to take on the work.
Alex
Cheers,
BruceC
On Jan 23, 6:58 am, Chris McDonough<[email protected]> wrote:
On Sun, 2012-01-22 at 11:53 -0800, Mike Orr wrote:
On Tue, Jan 17, 2012 at 11:21 PM, Chris McDonough<[email protected]> wrote:
On Tue, 2012-01-17 at 23:06 -0800, BruceC wrote:
Hi all, it would appear the current version of pyramid_simpleform
would be 0.6.1, which relies on Formencode, however I have spotted a
version 0.7 on bitbucket that Dan Jacob put together that also allows
a user to generate form schemas in Pyramid using Colander, which would
be my preference.
Does anyone know if pyramid_simpleform 0.7 is stable for use with
Pyramid (& Colander)?
It's not. I think it may be an evolutionary dead end at this point,
unless someone picks it up and runs with it.
What is at a dead end, and what do we need to to to ensure Pyramid has
a complete out-of-the-box option for form processing, ideally with
Deform/Colander but without FormEncode?
pyramid_simpleform + Colander is at a dead end.
colander + deform already works fine (deform depends on colander; it
cannot work without it).
"Complete out of the box option for form processing" is very much in the
eye of the beholder. There is no one solution to the problem. Some
people want pixel-level control over forms, which usually implies they
want to drive a form helper in their own templates. For other people
who have lots of forms, this would be a complete lose, because it's a
lot more valuable to have complete consistency across forms and easy
form rendering than it is to have aggressive pixel-level control over
how the form is rendered.
I'd considered trying to build simpleform-like capabilities into deform
as another mode. But considering I don't really use deform right now,
I'd hate to add more code to it that I don't actively maintain.
- C
--
Alex Clark ยท http://pythonpackages.com
--
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.
