#9025: Nested Inline Support in Admin
---------------------------------------------+------------------------------
Reporter: pixelcort | Owner: nobody
Status: new | Milestone:
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords:
Stage: Design decision needed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 1
Needs_better_patch: 1 |
---------------------------------------------+------------------------------
Comment (by schinckel):
I have got some code working, and attached a patch if anyone else is
interested.
Basically, I have slightly modified the ModelAdmin class to include the
nested inlines in the change page (I haven't worried about the add page at
this stage).
Then, the InlineModelAdmin has changes to create the inline formsets.
Finally, there are a couple of template changes, including a new template
for the nested formsets.
I have made a couple of design decisions that reflect my use case for the
project I am working on, mainly that I don't have add page support, and
only include the nested inlines in a TabularInline. Each class of inline
is a seperate column, and each instance of the related object is a sub-row
in that column.
I have an example image:
http://s3.amazonaws.com/ember/HGETbz2gS1IXvDlOB3idRmcp0ocFL1VK_l.png
(Note that this uses the Inline properties on this class to not show more
than 2, and none if the object is not saved).
--
Ticket URL: <http://code.djangoproject.com/ticket/9025#comment:26>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=.
