Sure, my bad, this is the example with form_business, a GFK, before / after: https://gist.github.com/jpic/c6a16723db62f779848f
If we make it to encapsulate value_from_object / save_form_data elsewhere than in the model field then it will allow form fields and forms used in the admin to do more. One might raise the point that there should only be one way for a form to get / provide data for a model field. While that makes sense, perhaps a pragmatic way to change it would be useful. Note that currently, I've tested the first idea (extension to modelform api) and maybe it's not that bad https://github.com/yourlabs/django-autocomplete-light/blob/v3/src/dal/forms.py#L60 Perhaps another way (deviated from the extension to modelform api) would be to have forms.models.ModelField classes, which would add the retrieve / provide data for a models.fields.Field and have precedence over the corresponding models.fields.Field.{save_form_data,value_for_object}: https://gist.github.com/jpic/c30724a5a90b258a312a Please let me know if there's anything else I can do to help getting feedback Thanks for your feedback -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CALC3Kadkg%3D3osehZMXFzx7E0rPfwDLQVn5adiev5QUSAgRKONQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
