Adam van den Hoven wrote:
> 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.

I completely agree. I wonder what Sean Cribb's perspective is on this?! 
I'd love to see him chime in.
-- 
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

Reply via email to