Use the form in the other post labeled as Survey: Also, I do agree I don't want everything to turn into a survey, but this is a point of contention that has been argued back and forth for months now ever since the feature "creeped" in without proper community input on this breaking change.
-Thadeus On Mon, Mar 22, 2010 at 10:54 AM, Iceberg <iceb...@21cn.com> wrote: > Well, we have enough discussion in > https://groups.google.com/group/web2py/browse_frm/thread/d25d13cd3f5bd7b1/67f5748c0411e81e > and I don't want to repeat. > > Just one thing. When talking about "keeping backward compatibility" > and thinking this argument could support proposal zero='', then you > are badly wrong. Actually I am the person who suggested the zero=..., > so I am quite sure that at the very beginning it was zero=None, in > order to be compatible with the earlier version of web2py which did > not have this feature at all! > > And, although I can admit that, in all my apps' code I explicitly use > zero='' more than zero=None, I still think zero='' is an EXTRA feature > that MUST be turned on EXPLICITLY. So... > > In short, I suggest zero=None as default. Period. > > > @Thadeus: Somehow I can not access your vote. So would you mind please > vote it for me? I choose "zero=None". > > Sincerely, > Iceberg, 2010-Mar-22, 23:06(PM), Mon > > On Mar22, 10:07am, mdipierro <mdipie...@cs.depaul.edu> wrote: >> I agree with Mr. Freeze but changing it now may constitute a breaking >> a backward compatibility. >> After reading the survey it has a lot of questions and it may >> confusing to a lot of users. >> Bottom line: >> >> zero='' is what we have now (vote for this if you do not want changes >> in your apps) >> zero=None is the change in behavior that Thadeus is proposing. It will >> change the way dropbox behave. It will eliminate the default empty >> option in the stopbox (vote this if you want the first alphabetical >> value to be selected by default). >> >> Clarifications: the last question asks whether the current solution >> (since 1.5x.x I think) was a breaking of backward compatibily, not >> whether a change now should be a braking of backward compatibility. >> @Thadeus, if you ask one question, you should ask the other too. >> >> Since there are quite a lot of questions I have to retreat what I >> said. I first want to read the answers and then decide what to do. I >> cannot automatically follow what majority wants since it is possible >> that people will make that case that change of behavior now will >> constitute breaking of backward compatibility. >> >> Massimo >> >> On Mar 21, 8:49 pm, "mr.freeze" <nat...@freezable.com> wrote: >> >> >> >> > Done. I personally prefer zero='' as a default. I think the selection >> > should be made explicitly by the user unless an actual default value >> > for the field is set. This doesn't break backwards compatibility IMO >> > because web2py wasn't controlling it before, the browser was. >> >> > On Mar 21, 8:26 pm, Thadeus Burgess <thade...@thadeusb.com> wrote: >> >> > > That is not a good point. That is a interface and usability question, >> > > also it is a clientell question of who will be using the app. >> >> > > I am tired of arguing this matter. As far as I see it, we broke >> > > backwards compatibility, forcing me to update all of my apps. >> >> > > I respectfully ask the community to please take the following >> > > anonymous survey on this topic. I will support the outcome of the >> > > results for this survey as the community decision. >> >> > > I will not take part of this survey since I created it. >> >> > >https://spreadsheets.google.com/viewform?formkey=dE5pd01zNndEMk4zREpF... >> >> > > -Thadeus >> >> > > On Sun, Mar 21, 2010 at 7:55 PM, mdipierro <mdipie...@cs.depaul.edu> >> > > wrote: >> > > > Not everybody agreed. Somebody (do not remember who) made a good point >> > > > that having zero=None will case people to fill forms with with wrong >> > > > values (always the first alphabetical value). >> >> > > > On Mar 21, 7:21 pm, Thadeus Burgess <thade...@thadeusb.com> wrote: >> > > >> Massimo, I think in the post everyone agreed to make zero=None the >> > > >> default, and yet after at least 13 of us said to make this the >> > > >> default, nothing happened. The original design was (is) a good idea, >> > > >> but making that a default was a bad idea. Nobody had any input at the >> > > >> moment, but after playing around with it, it sucks being the default. >> >> > > >> -Thadeus >> >> > > >> On Sun, Mar 21, 2010 at 1:00 PM, mdipierro <mdipie...@cs.depaul.edu> >> > > >> wrote: >> > > >> > There was a long discussion about this. Different people disagreed >> > > >> > on >> > > >> > how this should behave. >> >> > > >> > You can revert to the previous behavior with >> >> > > >> > IS_IN_SET(...,zero=None) >> > > >> > IS_IN_DB(...,zero=None) >> >> > > >> > Or customize the empty value >> >> > > >> > zero="Please choose one" >> >> > > >> > Massimo >> >> > > >> > On Mar 21, 12:42 pm, annet <annet.verm...@gmail.com> wrote: >> > > >> >> Today, I upgraded my web2py installation to version 1.76.5. In this >> > > >> >> web2py version the drop boxes display an empty key value pair >> > > >> >> first, >> > > >> >> and then the key value pairs from the tables I based them on. What >> > > >> >> causes this change in behaviour? How do I correct it? >> >> > > >> >> Kind regards, >> >> > > >> >> Annet. > > -- > 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 > http://groups.google.com/group/web2py?hl=en. > > -- 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 http://groups.google.com/group/web2py?hl=en.
