Sorry I misunderstood. Right now there is not deprecation warning on
anything I can remember.
On Mar 24, 4:39 pm, Renato-ES-Brazil wrote:
> I was talking about
> it:http://groups.google.com/group/web2py/browse_thread/thread/5574976535...
>
> On 24 mar, 16:48, mdipierro wrote:
>
> > No. They are
I was talking about it:
http://groups.google.com/group/web2py/browse_thread/thread/55749765353781f5/05298cdbca78f0db
On 24 mar, 16:48, mdipierro wrote:
> No. They are not officially "deprecated". It is just that there is a
> better way to do it. We will not stop supporting them. There is no
> re
No. They are not officially "deprecated". It is just that there is a
better way to do it. We will not stop supporting them. There is no
reason for any warning.
On Mar 24, 1:30 pm, Renato-ES-Brazil wrote:
> Ok. Right, but and the others functionalities deprecated? Are they
> registered as warning
Ok. Right, but and the others functionalities deprecated? Are they
registered as warning in log?
On 24 mar, 15:01, mdipierro wrote:
> no since they still work and will continue to support them.
>
> On Mar 24, 12:53 pm, Renato-ES-Brazil wrote:
>
>
>
> > Massimo,
>
> > Are the obsolete codes gene
no since they still work and will continue to support them.
On Mar 24, 12:53 pm, Renato-ES-Brazil wrote:
> Massimo,
>
> Are the obsolete codes generating warnings in any log? Where can I see
> them?
>
> Thanks...
>
> On 24 mar, 13:28, Abhishek Mishra wrote:
>
> > Alright I'll try looking for it,
Massimo,
Are the obsolete codes generating warnings in any log? Where can I see
them?
Thanks...
On 24 mar, 13:28, Abhishek Mishra wrote:
> Alright I'll try looking for it, Thanks
>
> On Mar 24, 9:21 pm, mdipierro wrote:
>
>
>
> > I wote a plugin for this last month and I posted on this list bu
Alright I'll try looking for it, Thanks
On Mar 24, 9:21 pm, mdipierro wrote:
> I wote a plugin for this last month and I posted on this list but I
> lost it. If somebody can find it please re-post it.
>
> Massimo
>
>
--
You received this message because you are subscribed to the Google Groups
I wote a plugin for this last month and I posted on this list but I
lost it. If somebody can find it please re-post it.
Massimo
On Mar 24, 11:14 am, Abhishek Mishra wrote:
> Okay, I will follow that way from now on.
>
> I have one more doubt,
> How do I pre-fill values in an autogenerated SQLFOR
Okay, I will follow that way from now on.
I have one more doubt,
How do I pre-fill values in an autogenerated SQLFORM? I tried looking
for it but couldn't find a way.
So, currently in the poll app I made -
page 1. user adds a new poll
page 2. once validated, it takes user to a page where he can a
yes
On Mar 24, 11:07 am, Abhishek Mishra wrote:
> Oh thats a nicer thing to do...
>
> So right into db.py I could write say
> db.poll.question.label = 'Question here'
>
> Could I ? :)
>
> On Mar 24, 8:26 pm, mdipierro wrote:
>
> > You do not specify the field labels at the level for the form
>
>
Oh thats a nicer thing to do...
So right into db.py I could write say
db.poll.question.label = 'Question here'
Could I ? :)
On Mar 24, 8:26 pm, mdipierro wrote:
> You do not specify the field labels at the level for the form
>
> form=SQLFORM(...,labels=...) # WRONG
>
> You specify them at
My answer was wrong. Your question was correct and I apologize.
I checked the code again.
I tried:
>>> SQLFORM(db.auth_user,fields=['first_name'],labels={'first_name':'Your
>>> Name'}).xml()
'Your Name'
and as you can say it works.
Still fields and lables are only there for backward compatibi
You do not specify the field labels at the level for the form
form=SQLFORM(...,labels=...) # WRONG
You specify them at the level of the fields
db.table.field.label='...'
form=SQLFORM(db.table)
Massimo
On Mar 24, 9:28 am, Abhishek Mishra wrote:
> Hi guys,
>
> I am trying to learn/try out w
13 matches
Mail list logo
