On 2/27/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > > On 2/27/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > On Feb 26, 3:15 pm, "Matthew Flanagan" <[EMAIL PROTECTED]> wrote: > > > Add to that > > > > > > 3. Finish Schema evolution and merge to trunk > > > 4. Finish Row level permissions and merge to trunk > > > > Actually, I think that the row level permissions will mostly be > > handled by the newforms-admin branch. > > 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? 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. > > Row-level permissions is all about setting modify/delete permissions > on a per-instance basis - e.g., preventing users from modifying or > deleting any blog entries that they didn't create. This general set of > features will be available anywhere, not limited to admin. > > For the record, I'd really like to see row-level permissions rolled into > Django. > > 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 -~----------~----~----~----~------~----~------~--~---
