On Fri, Sep 4, 2009 at 2:21 PM, andybak<[email protected]> wrote: > 1. I think worrying about projects vs. apps is a red-herring. We are > talking about a way to configure an admin app. There might be several > of these on a 'site/project/whatever'
Since this all seems to be specific to particular instances of AdminSite, AdminSite would be the logical place to do it if it's going to get code-level support. However... > 2. Some ability to regroup and choose better names is a biggie. It > pains me when I try and explain to my admins what 'auth' means... Practically everything being requested here is purely presentational. And Django has a component for doing presentational logic: the template system. The admin templates are deliberately easy to override with custom versions, and it feels like all of this is really just asking for things that are more cleanly done in templates. We (World Online) do this rather frequently, including shuffling things around, re-labeling bits, showing extra links to custom things we've added to particular applications. And we do it entirely in templates; it's not particularly hard. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
