Hi,
A way to fix this could be a custom Schema subclass that looked into
a hidden field with information about which fields are disabled. The
form should populate (and encrypt!) that hidden field when it's
displayed so the validator can skip validation on those fields that
are disabled.
However, this doesn't look very pretty to me so any other ideas are
welcomed... :)
The way ASP.NET solves this is the __VIEWSTATE hidden field. The state
of the controls is stored in that, and it is protected from tampering
using a MAC. As we start to do more complicated things with widgets
forms, I think a TG equivalent of __VIEWSTATE is inevitable.
Paul
--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---
