Jose
I suggest to change its default value back to None, so that old apps
behave in the same way.
Or at least, let the default value be empty string '', rather than an
English phrase "choose a value". The latter causes a developer have to
customize it again and again when developing applications targeting to
non-English end users.
Regards,
Iceberg
On 13 ene, 05:44, Iceberg <iceb...@21cn.com> wrote:
> I also notice this change.
>
> I suggest to change its default value back to None, so that old apps
> behave in the same way.
+1
Ok to make zero='' not to go back to zero=None.
--
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+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
Yes but technically, how would you do it?
Some constants strings are defined at the module level, i.e. they do
not belong to any specific application, while internationalization
strings are application specific.
I do not object to changing this. I just do not know how to.
> 2010/1/13 mdipierro <mdipie...@cs.depaul.edu>
>
>
>
> > There is no way to make everybody happy.
>
> > Ok to make zero='' not to go back to zero=None.
>
> > On Jan 12, 11:44 pm, Iceberg <iceb...@21cn.com> wrote:
> > > I also notice this change.
>
> > > I suggest to change its default value back to None, so that old apps
> > > behave in the same way.
>
> > > Or at least, let the default value be empty string '', rather than an
> > > English phrase "choose a value". The latter causes a developer have to
> > > customize it again and again when developing applications targeting to
> > > non-English end users.
>
> > > Regards,
> > > Iceberg
>
> > > On Jan13, 0:54am, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > > > IS_IN_DB(...,zero=None)
>
> > > > On Jan 12, 9:51 am, Jose <jjac...@gmail.com> wrote:
>
> > > > > How to remove the words "choose a value" of the dropbox?
> > > > > I want to work as before where it showed the first reading in the
> > > > > table.
>
> > > > > Jose
>
> > --
> > 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+un...@googlegroups.com<web2py%2Bunsu...@googlegroups.com>
To unsubscribe from this group, send email to web2py+un...@googlegroups.com.
On Jan 13, 2:25 pm, Thadeus Burgess <thade...@thadeusb.com> wrote:
> *the inherit problem of always keeping backwards compatibility*
>
> However, aside from this, there is a bug with the new "choose a value" that
> is unacceptable.
>
> http://static.thadeusb.com/choosevaluebug.png
>
> -Thadeus
>
> > <web2py%2Bunsu...@googlegroups.com<web2py%252Buns...@googlegroups.com>
On Jan 13, 2:25 pm, Thadeus Burgess <thade...@thadeusb.com> wrote:
> *the inherit problem of always keeping backwards compatibility*
backward compatibility aside. How would you do it?
There is a reason you have to call SQLFORM explicitly (or call crud
which calls SQLFORM) and it is not implicit. The reason that one may
not want to use it.
With a replacement you do not need to wory about backward
compatibility and may not need to use FORM validation mechanism at
all.
Massimo
On Jan 13, 2:59 pm, Thadeus Burgess <thade...@thadeusb.com> wrote:
> I'm not sure there is a good solution with the current design.
>
> At the moment, I am compiling a document with problem with the current form
> system. Along with the document I am also including topics that come up in
> the google groups and specific issues that continue to arise where the
> solution does not seem logical.
>
> When I feel that I have a solution that would work I will share this
> document. A working solution being something that sticks to web2py
> philosophy, and hopefully as backwards compatible as can be.
>
> -Thadeus
>
Please consider some blog posts toward an immediate goal of
redesign suggestions. As a new entrant into web2py, it
would be handy for me (and others) to understand where the
edge cases lay.
In the early days of Django, I wrote a lot of forms code
(pre-newforms) and I understand it's a difficult problem
to cover all the use cases. By putting your thoughts on
a blog, you might encourage comments from other people who
have different perspectives.
Best regards,
-Jeff