On Tue, 2010-06-08 at 00:55 -0400, Chris McDonough wrote:
It would be useful if the folks for whom it mattered could give this new
regime a roll before I merge it to the respective colander and deform
trunks and make new releases of both.
On Fri, 2010-05-28 at 08:28 -0400, Chris McDonough wrote:
I agree with how Tim just characterized this. I'm still trying to
figure out what the best way to spell it.
My current idea is to:
- Define a special null sentinel value.
- Change the type definitions and widget definitions to
On Fri, 2010-05-28 at 07:25 +0800, Tim Hoffman wrote:
From the point of view of the form definition, I think you need to be
able to define some type
of sentinal value that indicates a field is empty, but valid if it is
not required.
I think it would be a mistake to assume that default
We're doing a BFG app with a MongdoDB backend, and the Deform stuff seems
perfect for us, really enjoying using it so far.
But I can't figure out how to make a field in a schema optional if it's
not a String. (I've done this in Django model schemas where I can use the
flag null=True and
On May 27, 2010, at 3:24 AM, Chris McDonough wrote:
This is an area that I'm not 100% confident about yet, so I'm glad
you're stressing it a bit.
FTR, this definitely won't work:
SchemaNode(Integer(), required=False, allow_empty=True)
Because a SchemaNode does nothing with either
We're doing a BFG app with a MongdoDB backend, and the Deform stuff seems
perfect for us, really enjoying using it so far.
But I can't figure out how to make a field in a schema optional if it's not a
String. (I've done this in Django model schemas where I can use the flag
null=True and
