On Sep 5, 11:44 am, Iceberg <iceb...@21cn.com> wrote:
> my proposal does not prevent you from explicitly
> using default value at all. If you insist, you can still define
> default value as always:
> Field('language',
> requires=IS_IN_SET(['English','Chinese','Italian']),
> default='Italian') # the default value need not even be the first
> one
> And you know what? In my patch, the initial blank will be
> automatically hidden if you defines a default value. See the "if
> value" clause of my patch.
I'd missed that - useful, but still not quite there for me.
> After all, my proposal does not introduce any new syntax. Old apps can
> benefit from it, and can easily bypass it if insist. What more can you
> expect for? :-)
No unexpected behaviour in old applications when upgrading Web2Py.
This is one of the *key* strengths of this framework, whilst there are
some other goodnesses, sacrificing this shouldn't be undertaken
lightly...
F
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
