Hi all, Looks like my below post fell through the cracks; I'm hoping it's because everyone was busy preparing for DjangoCon, although I wouldn't blame people for skipping past my wall of text :) Does anyone have an opinion on recursive inline editing, one way or the other?
Regards, Jeff On Sep 4, 5:08 pm, Jeff Forcier <[EMAIL PROTECTED]> wrote: > Hi folks, > > I definitely remember this subject coming up before (possibly as far > back as magic-removal, even) but I'm either misremembering, or not > using the right search terms. Pointers to previous discussions/tickets > would be welcome. > > I'm imagining the ability to have recursive inline editing: e.g. in a > simple hierarchy of Model C has FK to Model B has FK to Model A, when > viewing the admin form for Model A, to not only have Model B as an > inline, but to have Model C inlined inside the fieldset for Model B, > allowing you to set up a slice of that entire hierarchy in one go. > > First: is this currently possible? It doesn't appear to be, based on > poking around the API for the ModelAdmin hierarchy, nor does it seem > possible to achieve it via forms/formsets (as there's no easy way to > have a single form/formset represent >1 model at a time, AFAICT). > > Second: if not possible, is it desirable? I recognize that with any > nontrivial hierarchy/number of extra objects per inline, the visual > representation could become ghastly. But assuming its usage is limited > to semi-trivial scenarios, it seems like the existing admin API could > be very easily extended to support this. I haven't done serious > investigation, but am thinking something like simply allowing/ > interpreting the 'inline' attribute on InlineModelAdmin (i.e. making > InlineModelAdmin more closely resemble a subclass of ModelAdmin, which > is probably the logical conclusion of this line of thought). > > (Also, I'm a large proponent of the "if the admin doesn't cut it, just > roll your own view/form/template" -- but this feels to me like > something that would be a natural admin feature, and widely > applicable.) > > Assuming I'm not missing something obvious, I'd be quite willing to > take a closer look at what would be required to implement this, and > put a patch together at some point if it appears feasible. Just want > to make sure I don't need a reality check first :) > > Regards, > Jeff --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
