I have shared my thoughts on these forums and have elected no response from
the community.
Recently other software projects have taken my focus away from web2py,
however I will be diving back into web2py projects
in a week or two, when I do this is one of the first tasks I will be working
on.
I w
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
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
*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
On Wed, Jan 13, 2010 at 9:32 AM, mdipierro wrote:
> On Jan 13, 8:02 am, Alexan
I always remember web2py needs to be more easier to internacionalize.
as example, delete_label in forms always have to be set to be able to
localize.
All strings 'under the hood' need to be T('string').
2010/1/13 mdipierro
> There is no way to make everybody happy.
>
> Ok to make zero='' not t
5 matches
Mail list logo
