On Mar 16, 2:18 pm, "James Bennett" <[EMAIL PROTECTED]> wrote: > And that distinction -- between Field-level > validation and Form-level validation -- also > makes intuitive sense to me; it feels right > that a Field only needs to know about itself,
I'm not particularly concerned about field validation and it generally works okay for me at the form level, but ... > while a Form is responsible for knowing about > all its constituent Fields and their interactions > (and, hence, validation which involves multiple > Fields goes at the level of the Form instead of > the level of the Field). But I think I understand a bit of Ian's frustration, though he may not have chosen the best use case to advance his argument. There are times that it would be convenient to access bound info at the field level. Witness the hack I perform in here in creating a BoundField instance, then assigning it as a faux attribute to a field: http://www.djangosnippets.org/snippets/82/ -- Jeff Bauer Rubicon, Inc. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
