There is no reason to make SQLFORM more complex than it is. Why not move some of the SQLFORM logic into a new object SMARTFORM(?) and behaves like FORM but accepts Fields as helpers and processes them like SQLFORM? parhaps SQLFORM could be derived from such a beast.
Massimo On Dec 15, 6:06 am, villas <[email protected]> wrote: > @Thadeus > Thanks for raising this topic. Tables don't seem correct for laying > out forms any more. So, should we assume that we're all heading in > the direction of fieldsets? Surely fieldsets should eventually be the > default. > > Maybe one way forward to is introduce a new option: > renderfieldset=False. If true we can get a fieldset and drag our > forms into the next generation! > > -David -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
