>
> OK, thanks. Tricky. My exposure to classes didn't get as far as the
> __call__ method.
>
Crud is also a callable class and works similarly to Auth. All of the
validators are callable classes as well. When you specify the validator,
you initialize it:
Field('fruit', requires=IS_IN_SET(['
OK, thanks. Tricky. My exposure to classes didn't get as far as the
__call__ method.
That explains how it works.
On Feb 8, 7:17 am, Anthony wrote:
> > Where would I add these?
>
> Add the links wherever you want them in your user interface.
>
> > I am really mystified how the auth() class call
>
> Where would I add these?
>
Add the links wherever you want them in your user interface.
> I am really mystified how the auth() class call receives the method as
> its argument from these urls assuming that the user action looks like:
>
> def user()
>return dict(form=auth())
>
Auth
Where would I add these?
I am really mystified how the auth() class call receives the method as
its argument from these urls assuming that the user action looks like:
def user()
return dict(form=auth())
How does this instance of the call to auth() get a method call?
I am really mystified abo
On Wednesday, February 1, 2012 12:23:54 AM UTC-5, Lewis wrote:
>
> Thanks.
>
> So, would I expand the default form to include buttons to access the
> other methods? Not sure how to expose those...
>
You just have to add links pointing to those URLs (e.g., URL('default',
'user', args='change_pa
Thanks.
So, would I expand the default form to include buttons to access the
other methods? Not sure how to expose those...
Guess I am ok on hashing but should probably look at using the key.
>
> The controller above exposes multiple actions:
> http://.../[app]/default/user/register
> http://.../[app]/default/user/login
> http://.../[app]/default/user/logout
> http://.../[app]/default/user/profile
> http://.../[app]/default/user/change_password
> http://.../[app]/default/user/ver
7 matches
Mail list logo
