jvanasco wrote: > Thats pretty much my sentiment too - unlike Robin though, I generally > don't like to use autogenerated html for fields - just leave that up to > the designer, and have them pull info from a dict. > > In TAL, its something like this: > === > <div class="f_error" tal:condition="Errors/email" > tal:content="Errors/email"/> > <input type="text" name="email" value="" tal:attributes="value > Defaults/_text/email"/> > Please Note: We will send a confirmation email to this address your > provide, and you must click on a unique confirmation link in that email > it to complete your registration. > === > Automagic generation saves time usually, but if there's some crazy > complex layout - i leave it to the css/html people to handle the form > placement. > > I'm looking forward to the .9a5 branch. The widgets seem great for > validation and , at times , for generation - but sometimes simplifying > things like that just makes it complicated to do a complex html form. > > I'm glad to know that what I didn't like about TG's approach to forms > can be ignored in .9a5
Actually (as I said on my last reply to Robin that I encourage you to look at) there is nothing new in 0.9a5 regarding widgets, just bug fixing and the rename of template_vars to params. Hence you can already ignore what you're talking about if you're using 0.9a4. Ciao Michele --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears -~----------~----~----~----~------~----~------~--~---
