Karl Guertin <[EMAIL PROTECTED]> writes: > And that is the mystery. I have been skating around this issue. There > should really be a 'required' attribute on the base widget. If true it > would add 'required_field' to the class so you can css it and would > set the validator to V.NotEmpty by default.
Or some way that allows one to change the class. It would be even better this way since you can specify classes for other circunstances besides required fields (or pass differente 'required_classes' for each widget...). > If a validator is passed in, that overrides V.NotEmpty. This means > that you can do something like V.String(if_empty = None) and secretly > make a required field not required, but I think this would work for > most situations. I prefer not touching validators. Just the class would solve the problem and allow for more customization. -- Jorge Godoy <[EMAIL PROTECTED]>
