On Fri, 2007-07-13 at 14:43 +1000, Malcolm Tredinnick wrote: > I'm -1 one on this for pretty much the same reasons as Adrian. It's just > not that big a deal even for people who want to work the way you do.
I should have re-subjected my second post, since I'm willing to accept the loss of a possible field named form in the model as sufficient reason for keeping form_for_instance and form_for_model outside the model space. My question for the rest of the second message was a question of how much separation between forms and models there should be. For me the validation issue is key. We currently don't have any standard way to programmatically validate model fields, but we can validate forms before we stick them into model fields. Seems like it'd be easy to avoid some duplication if we just admit the possibility that model fields can optionally specify something about their form fields. Todd --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
