Re: To Use or Not to Use the admin backend

> Anyway, to the question. Once the models, the intermediate models and
> the interactions between all of them start getting sufficiently
> complex, you will need to put new forms on front. Theoretically, you

I've a question about this. I tried to do something like this, but
using the main capabilities and hacking on the ModelAdmin classes,
changing the formsets and the like, and reusing as much as possible,
including of course the admin templates.

Of course, it wasn't possible. I was trying to do something as simple
as a double-indirection inline, a second-level foreign key, and ended
up just showing a link to the other model's admin page, creating,
indeed, a complex workflow where none was needed.

To what extent and how particularly would one need override a specific
admin page to do this kind of thing? Is reusing the templates at all
possible if you've customized things? Maybe the templates yes, but the
ModelAdmin views are impossible, I was in a hurry so I wasn't able to
do a good diagnosis of what would have been needed to do this.

Tomas

--
"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 django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.