If I've understood the arguments correctly, I think there are 3 good
reasons to keep as-is:
1. We should assume the average user to be as lazy as possible and
make as few clicks as they can. This means that with default=None the
first option will often be passively selected. i.e. many of your
Any more pros/cons on this?
Now is the time to weigh in your opinion.
--
You received this message because you are subscribed to the Google Groups
web2py-users group.
To post to this group, send email to web...@googlegroups.com.
To unsubscribe from this group, send email to
I do not really have an opinion on this. I am only reluctant to
changes in behavior.
Anyway, I am prepared to make this change (zero=None by default). I
would like to know that all major contributors are on board so that
you can answer the emails when users complain instead of me. ;-)
Anybody who
On Feb 4, 2010, at 7:08 AM, mdipierro wrote:
I do not really have an opinion on this. I am only reluctant to
changes in behavior.
Anyway, I am prepared to make this change (zero=None by default). I
would like to know that all major contributors are on board so that
you can answer the emails
Mind that currently zero='' should be interpreted as zero='(please
choose a value)'. the value '' is not in the db and will not pass
validation. It s just a place holder. Only if
IS_NULL_OR(IS_IN_DB(...zero='')) then the value '' can pass
validation.
On Feb 4, 9:25 am, Jonathan Lundell
On Feb 4, 2010, at 7:34 AM, mdipierro wrote:
Mind that currently zero='' should be interpreted as zero='(please
choose a value)'. the value '' is not in the db and will not pass
validation. It s just a place holder. Only if
IS_NULL_OR(IS_IN_DB(...zero='')) then the value '' can pass
This is a difficult to decide. For me it is both ways. Since half of
my forms require zero=None and the other half require zero='', either
way it goes there will be no option that is more convenient for my
development.
I stand in support of zero=None. Web2py is a data/business logic
oriented
^bump^
--
You received this message because you are subscribed to the Google Groups
web2py-users group.
To post to this group, send email to web...@googlegroups.com.
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com.
For more options, visit this group at
When saying some people ask for zero=None, some for zero='', some for
zero='Please choose a value', ok, I am the one who once suggest the
recent zero='' change, in this thread:
https://groups.google.com/group/web2py/browse_frm/thread/7a5154c377c9eec3
But hey, I think I made myself clear in that
Excellent suggestion on adding the comments with a link to the
discussion thread Iceberg
-Thadeus
On Sat, Jan 30, 2010 at 2:07 AM, Iceberg iceb...@21cn.com wrote:
When saying some people ask for zero=None, some for zero='', some for
zero='Please choose a value', ok, I am the one who once
bump
--
You received this message because you are subscribed to the Google Groups
web2py-users group.
To post to this group, send email to web...@googlegroups.com.
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com.
For more options, visit this group at
There is no way to please everybody here. some people ask for
zero=None, some for zero='', some for zero='Please choose a value'.
There is no right or wrong. I think we should leave the default as is
('', we changed it twice already) and you configure it as needed.
Massimo
On Jan 29, 9:00 am,
I must insist.
The point is that IS_IN_DB and IS_IN_SET now show a spurious empty
option by default.
The keyword here is default.
If you want to introduce a 'choose a value option you should do it
explicitly and 'at your own risk', the risk being that it creates an
option that when selected will
Let's hear a few more opinions. I don't just want to say no. The
problem is that we had this discussion already and people insisted
such option should be there.
Massimo
On Jan 29, 9:31 am, DenesL denes1...@yahoo.ca wrote:
I must insist.
The point is that IS_IN_DB and IS_IN_SET now show a
Yes, the option is important. But the case for a default of None is
pretty convincing.
On 1/29/10, mdipierro mdipie...@cs.depaul.edu wrote:
Let's hear a few more opinions. I don't just want to say no. The
problem is that we had this discussion already and people insisted
such option should be
+1 supporting DenesL argument. (but we already know this)
note.
default.
breaks app.
we like the feature
but it shouldn't break an app
no reason to have to specifically DISABLE something that hasn't
existed in web2py before ( you know, the empty select or please
choose a value breaks my app
I think the point is: is it better to generate a validation error
message when a choice is not selected or, by default, select always
the first choice? Are you sure that the problem is with the presence
of a blank option and not with the wrong error associated to it?
On Jan 29, 9:55 am, Thadeus
Thanks, I've seen it.
The problem with format and IS_IN_DB can be easily fixed in sql.py but
I would be against setting the default of zero to '' in IS_IN_DB and
IS_IN_SET if it creates an empty option in the dropdown.
zero seems to have been introduced to display a choose a value kind
of
My thoughts exactly :)
-Thadeus
On Thu, Jan 28, 2010 at 12:55 PM, DenesL denes1...@yahoo.ca wrote:
Thanks, I've seen it.
The problem with format and IS_IN_DB can be easily fixed in sql.py but
I would be against setting the default of zero to '' in IS_IN_DB and
IS_IN_SET if it creates an
19 matches
Mail list logo
