Then why you need form.py? You can always use templates to output form directly.
On Nov 6, 8:54 am, jgfoot <[EMAIL PROTECTED]> wrote: > Even better, why not have render take a template object, and let > authors just write templates that fill in the labels and input > controls wherever they want them? The current render() is icky > because it has HTML code, and many authors want 100% control over what > HTML code gets generated. > > On Nov 3, 11:04 pm, "Anand Chitipothu" <[EMAIL PROTECTED]> wrote: > > > > Sometimes, however, a little more flexibility is needed. Like having > > > the <label> in its own row. > > > How about providing render() for rendering with tables and > > render_css() for rendering with labels? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
