On 12/2/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > If I have to write my own interface, then what is the point of > the auto-generated one? This seems to goes against the philosophy of > Django. If this is the case, it would also seem that the admin > interface is so rudimentary that verges on uselessness.
Not at all. The admin interface is intended as just that - an _admin_ interface. A way of getting at a raw model definition, and tweaking the data. It is intended to get you off the ground quickly, not be a permanent fixture of your website. The intention of Django has never been to provide an 'out of the box, here is your website' experience - it is a framework to allow you to rapidly develop your own website, by giving you tools that make the development process as simple as possible. Writing your own views and templates isn't that difficult, and ultimately, your own view will always be more flexible and customised to your needs than the Django admin pages. > From what little I know, neither > model inheritance nor "multiple object acceptance" is possible. Model inheritance is possible, using the OneToOneField. I use this approach on a day-to-day basis in my Django projects. There are also modifications in the works to improve the capabilities of model inheritance within Django. Search the archives of this list and the wiki if you want to see what model inheritance will look like in the near(ish) future. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
