On 2/27/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > > On 2/27/07, Matthew Flanagan <[EMAIL PROTECTED]> wrote: > > > > On 2/27/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > > > > > > I might have missed something in the discussions somewhere, but I > > > don't think this is true. The newforms-admin is all about getting the > > > admin views into newforms, and breaking the admin views out of model > > > definitions. One of the side effects is that admin permissions will be > > > a little more customizable - but this won't have any effect outside of > > > admin. > > > > This is one of the issues I have with newforms-admin. Don't both the > > generic-auth and RLP branches cover what is being done here? > > No, they don't. At the moment, the admin interface uses oldforms. The > newforms-admin interface will use newforms. This is a major change > (hence the branch), but it is required because oldforms will be > deprecated in 0.96, and removed before 1.0. This is the major push > behind newforms-admin. > > In the process, we are taking the opportunity to remove the Admin > definition from the model definition (which is a long overdue design > change), and do some housekeeping that makes it easier to customize > the admin view, and deploy multiple admin views. > > Generic auth is all about allowing any other user login/authentication > scheme. Nothing to do with newforms, but the newforms-admin changes > should make it easier to integrate generic-auth with the admin > framework. > > RLP is all about having permissions on a per instance, rather than > per-class basis. Nothing to do with newforms, but the newforms-admin > changes should make it easier to integrate RLP with the admin > framework. > > > I don't > > see the point of adding something like this that can only be used in > > the Django admin. Django would be far more attractive to developers if > > this was a general set of features. > > Something like what? The port to newforms is required if oldforms is > to be deprecated, and this is the major push behind newforms-admin. >
Specifically, I was referring to the has_*_permission() stuff in the new ModelAdmin class. Which is new functionality aside from the oldforms to newforms port. > To boot, the admin features _are_ a general set of features. Most of > the newforms-admin port is about getting generic views and edit_inline > working properly with newforms, beacuse the admin app rely upon the > same tools that are available to every application. The only > difference is that the Admin application (and it is a normal > application like any other) is polished to allow some very specific > customization options that are useful in an admin context, and comes > with some pre-canned templates that are all perty. > > Yours, > Russ Magee %-) > > > > -- matthew http://wadofstuff.blogspot.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
