Permalink
Browse files

Merge pull request #170 from timrichardson/sqlform_bootstrap_style

SQLFORM formstyle can also be bootstrap
  • Loading branch information...
2 parents b15db39 + fa57411 commit c0b8898b69e03607d2e99eaf137e974735f1d796 @mdipierro mdipierro committed Feb 20, 2014
Showing with 1 addition and 1 deletion.
  1. +1 −1 sources/29-web2py-english/07.markmin
@@ -453,7 +453,7 @@ col3 = {'name':A('what is this?',
- ``readonly``. If set to True, displays the form as readonly
- ``comments``. If set to False, does not display the col3 comments
- ``ignore_rw``. Normally, for a create/update form, only fields marked as writable=True are shown, and for readonly forms, only fields marked as readable=True are shown. Setting ``ignore_rw=True`` causes those constraints to be ignored, and all fields are displayed. This is mostly used in the appadmin interface to display all fields for each table, overriding what the model indicates.
-- ``formstyle``:inxx ``formstyle`` determines the style to be used when serializing the form in html. It can be "table3cols" (default), "table2cols" (one row for label and comment, and one row for input), "ul" (makes an unordered list of input fields), "divs" (represents the form using css friendly divs, for arbitrary customization). ``formstyle`` can also be a function that takes (record_id, field_label, field_widget, field_comment) as attributes and returns a TR() object.
+- ``formstyle``:inxx ``formstyle`` determines the style to be used when serializing the form in html. It can be "table3cols" (default), "table2cols" (one row for label and comment, and one row for input), "ul" (makes an unordered list of input fields), "divs" (represents the form using css friendly divs, for arbitrary customization), "bootstrap" which uses the bootstrap form class "form-horizontal". ``formstyle`` can also be a function that takes (record_id, field_label, field_widget, field_comment) as attributes and returns a TR() object.
- ``buttons``:inxx ``buttons`` is a list of ``INPUT``s or ``TAG.button``s (though technically could be any combination of helpers) that will be added to a DIV where the submit button would go.
For example, adding a URL-based back-button (for a multi-page form) and a renamed submit button:
``

0 comments on commit c0b8898

Please sign in to comment.