Yeah, this seem to be ancient, maybe it is left for the backward compatibility.
But there is also render_css, that is tableless. I think anyone may have his own preferred way of form's html structure, its really impossible to have universal solution. So I go with the Form subclassing. On Wednesday, June 13, 2012 2:53:47 PM UTC+4, drx wrote: > > I agree, tables are ancient practice, and because webpy uses them I never > bothered to use the built-in form functions. Would love to see this > changed. > > Am 13.06.2012 03:09, schrieb [email protected]: > > I edited my form.py to render with fieldsets and legends rather than > > tables. Would anyone else be interested in this? It's (arguably) > > better HTML practice, would there be any interest in moving this into > > the main version of webpy? I'm happy to contribute if there's > > interest. If not, well, no worries :) > > > > -- > http://noobz.cc/ > http://digitalfolklore.org/ > http://contemporary-home-computing.org/1tb/ > -- You received this message because you are subscribed to the Google Groups "web.py" group. To view this discussion on the web visit https://groups.google.com/d/msg/webpy/-/KkPmb2zW2F0J. 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/webpy?hl=en.
