Assuming you don't need the fieldset and legend (which don't look useful in this example), I would think the Bootstrap styling would still work fine with the web2py form. If you really need to restructure, though, then creating a custom form should be fairly easy: http://web2py.com/books/default/chapter/29/7#Custom-forms.
Anthony On Tuesday, January 10, 2012 4:52:22 PM UTC-5, David J wrote: > > Yes sorry for the confusion > > Here is an example from twitter: > > <form> > <fieldset> > <legend>Example form legend</legend> > <div class="clearfix"> > <label for="xlInput">X-Large input</label> > <div class="input"> > <input id="xlInput" class="xlarge" type="text" size="30" name="xlInput"> > </div> > </div> > </form> > > Here is the web2py output. Having trouble changing using web2py elements(). > > <form class="form-stacked" method="post" enctype="multipart/form-data" > action=""> > <div id="auth_user_first_name__row"> > <div class="w2p_fl"> > <label id="auth_user_first_name__label" for="auth_user_first_name">First > Name: </label> > </div> > <div class="w2p_fw">Message</div> > <div class="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 > > >
