I've seen a suggestion against using the data model's FormEncode
validator as the widget validator.  Why would this be a bad idea?  A
validator that worked with both the model and view would avoid
duplication and make CRUD interfaces richer.

Reply via email to