Hi,
Just in case it helps you (or any other). For our projects (and
plugins), we separate actions based on "object ownership". I mean, we
have three separated namescopes: "site" (no namescope), "member" and
"admin". Admin is quite clear, are the actions for global site
administration, but there is a "tricky" difference between "member"
and "site".
- "Member" isn't just "for login_required actions", but for the "owner
of the object". That is, the moderator of a group if talking about
groups, the member of a group if talking about a membeship, the author
of a post, the user who is going to attent an event if talking about
attendances in tog_conclave.
- "Site" are "all other actions".
The main reason for this is that we build the site around the content
and it's ownership, not the role an user has in the appplication
(social applications). And in the few cases we needed some different
roles, it was application's specific features, and we developed
specific controllers and models for this, but we have make this only
once.
That said, as Richard said, admin column should be replaced easily by
a more complete role support. We haven't given much thought to this
issue, since we haven't needed it yet. We have talked about it time
ago, but nothing done. But you won't find any support for roles in the
developed plugins outside this namescope separation right now.
What kind of site are you developing?. Do you need many roles?. Tell
us if we decide to integrate some plugin and we can help you.
--
Alberto Molpeceres.
Linking Paths.
Find us at
http://www.linkingpaths.com