I think you've hit on something.
its probably reasonable to assume that the common default installation
is going to be someone who's using it for their own website. One user
means one role so take the admin/developer/user behaviour out and move
everything into an extension. That extension would be an expanded
version of page group permissions. The only thing I would do is
configure the core behaviour such that any other extension developer
could specify group permissions without requiring a group extension
installed (sort of how the help extension allows developers to add
Help without requiring that help exists). Radiant can specify a core
API for the role behaviour (so that anyone can create any role
extension they desire) so that we can all work together.
I'd actually suggest doing the same thing for user management. That
would allow us easily create an OpenID user extension or extend users
from Admin into pages. But that's a different thread.
On 7-Aug-08, at 9:33 AM, Arik Jones wrote:
Why isn't anyone extending on top of Page Group Permissions. I think
that framework can be used across the board. What do you guys think?
Personally I think the role administration in Radiant is rather
lacking
and for good reason. However, the rest of us need something. I love
what
Page Group Permissions has done. Solved a huge problem. But I think it
could use some expansion in terms of what you're giving permissions
to.
Maybe eventually it could replace the current core role admin scheme.
Thoughts?
--
Posted via http://www.ruby-forum.com/.
_______________________________________________
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
_______________________________________________
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
