Hello,
Ticket #10938 [1] suggests declaring inlines in fieldsets, and was closed as
wontfix.
I think this ticket mixes two different things:
(1) make it possible to *declare* inlines in
ModelAdmin.fieldsets instead of ModelAdmin.inlines. This is a bad idea:
there should be only one way to declare inlines, and the current way is OK.
(2) make it possible to *include* inlines in ModelAdmin.fieldsets (with
a syntax that's still to be defined) in order to chose the position of the
inlines in the change form. I think it's useful; actually, I need that right
now.
Currently, inlines are added at the bottom of the change form — see
templates/admin/change_form.html — and displaying them in another position
involves re-ordering things with javascript or overriding the change form
template. It would be easier if fieldsests accepted both fields and inlines
in fieldsets.
Reading Russell's closing comment, it looks like he had (1) in mind but not
(2). Does the wontfix also apply to (2)?
Best regards,
--
Aymeric Augustin.
[1] https://code.djangoproject.com/ticket/10938
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
