I agree that there are some good things in the acl/ auth section, but it is the area that so many people crash in, sometimes I think there almost needs to be a wrapper for them that makes it easier to get started with, but then the inevitable complaints about constricting the application....
I think some looking at making it more concrete around some real uses. Maybe even tieing into the bakery code since it is open and on the forge.... I think part of the issue is that it is not an easy thing to do in any way. The whole set of mental models that people have around Authentication and authorization (and acl as a frame for that) just gets people all tied up in knots Sam D On Tue, Jul 1, 2008 at 11:41 AM, Jonathan Snook <[EMAIL PROTECTED]> wrote: > > I think I'd say somewhere in the middle. I think much of the Lord of > the Rings intro is okay but maybe a little verbose and not directly > applicable to anybody's project. Using an example like a standard > User/Group permission system would be easier to understand. > > I like the way the section is ultimately structured but it needs more > examples, especially in the context of how they are used with > controllers and actions. They should especially be examples that could > almost be copy-pasted into a project. > > -Jonathan > > On Tue, Jul 1, 2008 at 1:15 PM, John David Anderson > <[EMAIL PROTECTED]> wrote: >> >> 1. Rewrite ACL (parts of Auth) documentation from scratch. >> >> 2. Keep what's there and update it. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
