extend the admin.ModelAdmin class

[GoogleCodeExporter]

I'm a newbie on this, but maybe it could be better if in the admin.py use a
subclass of ModelAdmin to use this great tool, instead of the
make_ajax_form call.

Original issue reported on code.google.com by peil...@gmail.com on 23 Feb 2010 at 12:37

[GoogleCodeExporter]

actually the admin doesn't specify fields or widgets, it only has a fieldsets 
var which references fields by name 
and the Form must specify the fields/widgets.  in all cases custom fields and 
widgets are specified in the form 
class.  the form class handles the form and processing the form.  the admin is 
related only to the admin site 
and basically is just an extra wrapper on the form and has some code for 
connecting with the rest of the admin 
site.

also, there is an assumption in the django community that the Admin does 
everything always.  forms are often 
used outside of the Admin site, and in general I don't let people in the admin 
site at all.

hope that helps

Original comment by crucialf...@gmail.com on 23 Feb 2010 at 4:16

• Changed state: WontFix

[GoogleCodeExporter]

ok, thanks. 
Anyway, I think in the django admin is not well resolved the many2many and 
foreignKey
relationships, specially when one of the related tables has thousands of rows.

Original comment by peil...@gmail.com on 23 Feb 2010 at 4:41