New Restrict Dialog

1. pass #1
1. 1.1. benefits
2. 1.2. pitfalls

issues:

generic vs. specialized?
exposing the value of roles?
hardcoded roles names
how to deal when roles are changed (what if all flags were removed from contrib?)
support for "advanced" perms from other sources? (blech)

pass #1

(i'm missing the recurse to children checkbox - it would be on the bottom)

benefits

keeps the same concepts in place - public, semi-public, private. solves most uses cases we've seen forums (view + editor differentiation), relatively compact ui. keeps the end-user from having to understand roles and permissions. tab names may not be clear enough.

pitfalls

not a true generic implementation - will not solve more specific granular use cases, like "attach but not edit". will not fix issues if somebody custom posts permissions. tabs might be confusing. if admin changes the values of contributor or viewer, could be problematic. removes <select> form, so we'll have to write our custom control for the user list.

Retrieved from "http://wiki.developer.mindtouch.com/User:RoyK/New_Restrict_Dialog"

Tag page
What links here

New Restrict Dialog

Table of contents

pass #1

benefits

pitfalls

Files 0

Images 1

Table of contents