The admin templates and views themselves are convoluted enough (the
price of having them work with anything), and full of enough magic
that it's not really feasible to build on top of them to add the
required capabilities. Maybe adding new admin views would be a
posibility, but what happens when you want an admin page that does not
exactly correspond to a given model? You can usually twist things
around to make it so, but the fact stands that the admin is in the end
just a way of managing the database, and that the user must *really*
know what they're doing to avoid screwing up big time. Maybe careful
permission handling and/or different admin site instances are a
(partial) solution to this, but I haven't played with those myself.
--
"The whole of Japan is pure invention. There is no such country, there
are no such people" --Oscar Wilde
|_|0|_|
|_|_|0|
|0|0|0|
(\__/)
(='.'=)This is Bunny. Copy and paste bunny
(")_(") to help him gain world domination.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
