Yes sorry for the confusion
Here is an example from twitter:
<form>
<fieldset>
<legend>Example form legend</legend>
<divclass="clearfix">
<labelfor="xlInput">X-Large input</label>
<divclass="input">
<inputid="xlInput"class="xlarge"type="text"size="30"name="xlInput">
</div>
</div>
</form>
Here is the web2py output. Having trouble changing using web2py elements().
<formclass="form-stacked"method="post"enctype="multipart/form-data"action="">
<divid="auth_user_first_name__row">
<divclass="w2p_fl">
<labelid="auth_user_first_name__label"for="auth_user_first_name">First
Name: </label>
</div>
<divclass="w2p_fw">Message</div>
<divclass="w2p_fc"></div>
</div>
On 1/10/12 4:47 PM, Anthony wrote:
On Tuesday, January 10, 2012 4:14:02 PM UTC-5, David J wrote:
Thanks I think the semantics for forms is quite different from web2py.
I think it may be easier to use custom forms vs trying to do it
this way.
Are you talking about Twitter Bootstrap? I thought that just provided
CSS styling for form elements. What does it do that isn't compatible
with standard web2py SQLFORM rendering?
Anthony
