Re: [xwiki-users] [xwiki-devs] [Proposal] Rights Management UI

The inheritance is a little bit particular, since allowing a given right

lower level, will deny that same right for anybody else even if this

is allowed at a higher level.

Hi, Did: - source of inheritance is per rights; - local source of inheritance: if the a right is allowed to anyone else

the same level, it is implicitly disallowed for any others; - inheritance from upper levels / groups. Please see if I put the rights correctly: Wiki Level: http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights41Wiki Space Level: http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights41Space Obs. Summary view + icons not done yet. Thanks, Caty On Sat, May 22, 2010 at 11:31, Denis Gervalle <dgl(a)softec.lu> wrote: > Hi Caty, > > This one is simpler and more easy to understand than proposal 2 (which I > liked but were complex). It is your best try IMO. I agree with Caty that > using icons too reduce the place taken will not allow easy extensions.

> Alex proposal would help to have a summary view, which is nice to have > too. > > Maybe we could do both in fact. Propose a summary view (by default),

> fit a single line per user, this view would present the common rights > (V/C/E/D/A/(R/P)) using icons, and a last icon would be used to mention > there is more special rights either inherited, allowed or denied. So we > only > need to use (and think about) a short icon representation for common > rights, > and extended rights will be represented by a single special > representation. > Rows could be expanded individually or globally so if you want a more > detailled information, you may reach it either for a single user or all

> once. Changing common rights would be allowed in collapsed mode and > expanded > mode, but changing special rights would only be allowed in expanded

> > If you want to keep the width even smaller, you may also colspan the > user/group column over the others, using 2 rows per user, but I am not > sure > it will be nice. (Could this be only when horizontal space is short ?) > > I really like this one because it is simple to learn without

> and could also help learning how rights works, but there is again > some inconstancies with the current implementation. Compare to proposal

> these inconsistencies may be nicely fixed and really helps understanding > why > the right is disallowed at any time. You can do it like this: > > - the inheritance pop-up information should be at the right level in > the inheritance columns. The rights are inherited and check

> so > the precise source of inheritance is per rights, not only per user or > group > - there is a local source of inheritance: if the a right is allowed to > anyone else at the same level, it is implicitly disallowed for any

> So the source of inheritance is the local level, implying a deny because > the > local level has at least a specific allow. This means than when you drag > the > first time a right in the allow column, all other user/group at the same > level will have that right inherited deny from the current level. (For > those > who wonder and will check the source of the right service, yes, there is > potential performance improvement by immediately denying when a > non-matching > allow is found, currently we continue to check right at higher level for > more deny, this is not really clever) > > With these changes, I really feel that this last proposal could be a

> improvement in the way rights are applied, and keeps the interface

> at > the same time. > > WDYT ? > > Denis > > On Sat, May 22, 2010 at 07:57, Ecaterina Valica <valicac(a)gmail.com> > wrote: > > > On Fri, May 21, 2010 at 21:42, Alex Busenius <alex.busenius(a)xwiki.com > > >wrote: > > > > > I like this version, it makes clear what is allowed/denied and why, > but > > > it takes a lot of space. What if those rights names would be

> by > > > big icons and placed side by side? Like this (sorry for ASCII-art): > > > > > > -------------------+-------------------------------------+--+------ > > > Unregistered users | [+V] [+C] [+R] [-D] [-A] [-P] [-CC] | | [-E] > > > > > > > > Big Icons: > > We are using Silk set for our icons and this is constraining. Also, > Rights > > version 3-4 were made having rights extensibility in mind, for use

> > like adding "captchaComment" right, or "annotate" right, or > > "applicationXusage" right .... so I don't think is very good if > > applications > > are gonna have to choose their custom icon to represent their custom > right, > > because is gonna be a mess in the UI. > > > > There are few possible icons to choose from (in order to keep the > look&feel > > unitary) and having the developers choose their own icon for the right > they > > extend is gonna break the UI consistency. > > I think is much easier, extensible and less visual cryptic to textual > > describe an extensible right. > > > > Placed side by side: > > Version 4 takes a lot of space, yes, but the problem with side by side > is > > that is less readable (harder to scan the rights order). Also it's > easier > > to > > have a bigger area to select when you want to drag an item. > > > > Thanks Alex for your feedback, > > Caty > > > > > > > > Alex > > > > > > > > > On 05/21/2010 07:51 PM, Ecaterina Valica wrote: > > > > Hi, > > > > > > > > Changes: > > > > > > > > - One additional column is added: "Default / Inherited Rights", > by > > > > default all rights appear in this column > > > > - By using drag'n'drop items are tossed around between "Allow > > rights", > > > > "Deny rights" and "Default / Inherited Rights" > > > > > > > > Rights Proposal 4: > > > > > > >