Paul Johnston <[EMAIL PROTECTED]> writes:
One design aspect I do feel strongly about is that the secure mode should be the default. A programmer should have to explicitly turn off security if they want to do some fancy things. If we get the design right though, most client-side manipulation will just work alongside the security.
The problem is how much extra traffic this will cause. If it is just extra traffic on submission then I agree. If there's extra traffic other times -- e.g. when an option is selected / deselected -- then I believe this should be turned off by default.
I noticed the mention of changing the form based on what options are selected. I submitted a widget along these lines called HidingSingleSelectField, which I use a fair bit. Another widget I am looking at is a SecurePassword field, which is write-only - the value cannot be read from the web app.
It just encapsulates the JavaScript needed to hide it or does something else besides that? -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
