#1905: use variable_decode to add automagical formparsing like tg1
------------------------+---------------------------------------------------
Reporter: mramm | Owner: anonymous
Type: defect | Status: new
Priority: normal | Milestone: 2.1
Component: TurboGears | Version: trunk
Severity: normal | Resolution:
Keywords: |
------------------------+---------------------------------------------------
Comment (by nickmurdoch):
First time I accidentally encountered this in TG1, it was a bit
bewildering as I wasn't expecting my form names to be played around with;
however once I knew about it, it was very useful for contructing forms
that could be easily worked with in the controllers.
A decorator (or argument for expose()?) to optionally provide this
functionality would be nice to have, although I suspect it'd be trivial to
write one myself! Although it did take me a good few hours to work out
what in TG1 was actually responsible for causing this behaviour before
being able to even find this ticket -- it's quite a difficult concept to
put simply into words.
--
Ticket URL: <http://trac.turbogears.org/ticket/1905#comment:5>
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.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---
