Note, if you just want to make minor tweaks to the standard SQLFORM output,
you could just do server-side DOM manipulation. And if you have a standard
custom form layout, you could write a custom formstyle function to pass to
SQLFORM.
Anthony
On Saturday, October 19, 2013 7:36:26 PM UTC-4, Anthony wrote:
>
>
> {{=form.custom.begin}} in the beggining and
>>
>> {{=form.custom.end}} in the end.
>>
>> it seems that having to write form.custom.widget. for every field seems like
>> a lot of typing
>>
>> couldnt it be ommited?
>>
>>
> What exactly do you want to omit? If you omit the .begin and .end, do you
> expect web2py to know where in the HTML to insert the opening and closing
> form tags? How would it know? If you omit a particular widget, do you
> expect web2py to insert it for you? Again, how would it know if and where
> you want it? What would you like your code to look like, and what would you
> like the final HTML output to look like? Bonus points if you have ideas
> about how your proposed change could be implemented?
>
> Anthony
>
>
--
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
