#626: [PROPOSAL] Small forms refactoring to make them more useful and easy to
customize
-------------------------+--------------------------------------------------
Reporter: alberto | Owner: anonymous
Type: enhancement | Status: closed
Priority: normal | Milestone: 0.9
Component: Widgets | Version:
Severity: normal | Resolution: fixed
Keywords: |
-------------------------+--------------------------------------------------
Comment (by alberto):
Hi Michele,
I'm migrating some forms to the new style (you broke my apps, bastard ;)
and I've got something to point out, it has a comment that says it's going
to be deprecated, but anyway...
Shouldn't be "field_for" (or whatever replaces it) in FormFieldsContainer
so it works for any kind of container?
I read somewhere that you were thinking about a {{{
widget.display_field_for("form.bla.blou") }}} syntax. Seems like a good
idea to me, as it'll let us have total control over the layout. Do you
want me to give it a shot or are you planning to do it somewhen soon?
Thanks again :)
Adeu,
Alberto
--
Ticket URL: <http://trac.turbogears.org/turbogears/ticket/626>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears Tickets" 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-tickets
-~----------~----~----~----~------~----~------~--~---
