Hello,
I often find an app consists of one main model and serveral subsidiary
models linked to the main model by a foreign key. The django admin
system by default treats all of these models the same- ie they all
appear in the app's index on the same 'level'. The alternative is to
use inline forms to display these models but sometimes the subsidiary
models are to big or too numerous for this too be practical.
A solution to this would be make a new mechanism to register 'sub'
model admin classes with a 'super' model admin object in a similar
manner to inline forms, and use the same add, change and list views
but beneath the parent model with the foreign key field automatically
set.
Example uls:
The sub model change list page:
/admin/app_index/super_model_label/super_model_id/
sub_model_label/
The sub model change page:
/admin/app_index/super_model_label/super_model_id/
sub_model_label/sub_model_id/
Has anybody else considered this problem or have any suggestions?
Sam
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
