On Mon, Jun 20, 2011 at 7:51 PM, Aymeric Augustin <aymeric.augus...@polytechnique.org> wrote: > 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)?
Hi Aymeric, Apologies for taking a while to get back to you on this. You're correct -- I had (1) in mind when I wontfixed the ticket. However, I can certainly see the merit in interpretation (2) providing a way to include inlines in fieldsets as an organizational/ordering mechanism. This general feature request (i.e., ordering of inlines within normal field organization) is something that has been proposed several times in the past -- in fact, I'd be surprised if there isn't a couple of tickets relating to this. Of course, the devil is in the details -- especially, in finding a good syntax given that there isn't a name or label currently available for referencing inlines... Yours, Russ Magee %-) -- 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.
