9 Jun
2010
9 Jun
'10
12:36 p.m.
> >
> > > > It will if it display the inheritance source in a column. For
right
> > set
> > > > at
> > > > > current level this column could even precise what inheritance
been
> > > overwritten, both in terms of allowance and origin.
> > >
> > > Denis.
> >
> >
> > Hi Denis,
> >
> > "Something" like this:
> >
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights51Space
> >
> >
>
> > Yes, "something" like that. I would have expected a "back to
basic"
> button
> > in place of "advanced, and the removal of the basic interface to > > > advanced interface, I do not know.
Also add some hyperlinks to
upper
>
level
> > in the column explaining inheritance. And put the highlight of
changes
> > over
> > > the rest of the row (includes name and inheritance)
> > >
> >
> > >
> About:
>
> > I would have expected a "back to basic" button
> > in place of "advanced, and the removal of the basic interface to
avoid
>
duplicating basic rights
>
> >
> > This removal of the basic interface will be set from the user
profile's
> > variables (if it has advanced type)?
>
>
> No, just removed when the advanced interface is shown using the
advanced
button,
like you have done.
user"
> in their profile, will not be presented the advanced interface link, I mean if the user is advanced, all the
rows will be presented in advances?
No, the only thing I proposed is that user that are not set "Advanced will
never see extended rights.
> I'm asking because I think the collapsed view is great to see changes
up
in
deep
> complex stuffs
>
>
> >
> >
> > > WDYT ? Is this interesting ?
> > >
> >
> > it's nice :P I would love to see some other opinions.
> >
>
> Yes, could it be possible for you to fix the interactive version to the table, where you don't care the advanced
status of those rights.
I completely agree. Advanced interface is for understanding and fixing > the
> basics and also to have hover and click work as expected. I think it
will
helps in
receiving more feed back with causing confusion.
Raluca offered to help me fix the interaction.
> I found the result really well suited now. There is just some > in
> color contrast, icons aspect, and so on that should be applied if we
get
approval
for this proposal.
Once you have fixed the sample, I think that a summary page (resume of
our
> reflexion, and containing only the final proposal) and than a vote > could be appropriate to receive feedback
from other committers, since
the
size of
this thread could be pushing back.
Yes, a summary+vote is needed.
I made a version with pagination and filters added.
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights51Space
PNG for the filters:
collapsed:
expanded:
http://incubator.myxwiki.org/xwiki/bin/download/Improvements/Rights43Propos…
What do you think?
Could this filters be helpful? Are too powerful/complex/useless?
Not sure we really need all these. What is important for me is:
- local, global, all user type, with local by default
- local, inherited, implied right
- user/group name filtering
The rest could be convenient, but it also takes unnecessary horizontal
space, which is annoying IMO.
IMO, when no right has been set is a special case, the Default values. We
could see it as implicit, but actually I think they are more like inherited
(from the code values :P ).
Another question: The local source of inheritance (if a right is allowed to
anyone else at the same level, it is implicitly disallowed for any others)
is gonna be seen as implicit or locally set?
For example allow for evalica on view right is going on the "locally set",
but implicit deny on view right for UnregisteredUsers and RegisteredUsers is
going where? (locally set or implicit)
Practical is only for this level, so it's local. But it is not set
explicitly by the user, so it must by implicit.
Thanks,
Caty
From an implementation point of view, can a
livetable have more than one
filter per a column.
No problem if we use only the .js without de livetable macro.
Anyway this will be a custom livetable, because
we also
need to integrate the "add user" part and the "save/reset" buttons.
Yes, it will probably be so.
Also, from an implementation point of view,
should we enable multiselect
(ex. to select multiple rights)?
I have made recent fixes for that in the livetable.js, so this is not a
problem.
Obs. Right -> Sources -> Implicit refer to
the rights that come from the
setting of another right (example: admin means implicit
view+edit+delete+comment; creator means implicit delete). Would this
filter
option be useful or it is too much?
Doesn't this also include implicit settings when no right has been set
anywhere ?
Denis