>
> Personally I prefer python to javascript so would render server side
>> myself.
>>
>
> Keep in mind that with the new system, you won't necessarily have to write
> Javascript -- the Javascript that renders the forms will be provided by the
> framework.
>
I am thinking of those occasions where the default rendering doesn't suit
my needs. For example the table layout doesn't work when I wish the labels
to go above the form fields, so in these situations I have a custom form
view.
>
>
>> I do think SQLFORM offers useful features but I sometimes end up
>> discarding all the generated html to use my own custom view, which means
>> wasted processing time on the server.
>>
>
> Note, if you don't do {{=form}} in the view, then the form is never
> serialized into HTML (though the server-side DOM is created, so there is
> still some waste if you're not using any of the HTML or widgets).
>
I didn't know that. Thanks for pointing this out. If I define custom forms
using:
{{=form.custom.widget.name}}
for example, does the whole form get serialised then, or just the relevant
widget?
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
