On Thu, 22 May 2008 09:32:40 -0700, jonknee wrote: > On May 21, 9:33 pm, "James Bennett" <[EMAIL PROTECTED]> wrote: > >> Well, newforms-admin is being written to make the HttpRequest object >> available as an argument to the various ModelAdmin methods, which means >> that when you set up your own custom admin you can do pretty much >> anything you want. >> >> Which will make a lot of people happy, and let them go right on >> building workflows that don't make a lot of sense (if somebody's a >> trusted administrator, how come you don't trust them to fill in a field >> properly?). >> >> > I agree with you in theory, but it has some merit in practice. If you > have a lot of admins (let's say 20+), selecting through a large list of > users is time consuming and error prone. I'm OK with writing custom > views for edge cases though. > Agree in theory as well, but practice is almost always different. No bigger client will agree with "they're trusted" argument, none of my clients do, and I end up creating separate, custom-built admin interfaces for this group and that group of users.
Admin is just a contrib app, made for a specific use-case, so I'm not complaining, and I understand the MVC separation of concerns, but I secretly wish that there was a straightforward, optimized and documented way of dealing with this very common need for a model instance to know who's messing with it. This probably doesn't belong in the model, but for now, I'll stick with threadlocals.get_current_user() until I take a closer look at using newforms-admin. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
