19 Nov
2008
19 Nov
'08
2:43 p.m.
On Tue, Nov 18, 2008 at 11:51 PM, Lukas Renggli <renggli(a)gmail.com> wrote:
- The original version of Pier-Security used to have a
split according
to chmod/chown/chgrp, however in pratice it has shown to be less
meaningful and forcing users to apply different commands for one
action. I found this split very powerful for sites like ese.unibe.ch
where there are many different groups (admin, assistant, student,
team-1, team-2, team-3, team-4) and lots of different users.
Makes sense. Maybe it's just a problem of presentation then, or
providing links, e.g. so that you don't lose focus when you want to
change the owner of a page, and "oh right, I need to create it before,
with an associated group"
- Indeed copy/move are extremely similar (we should
have links too). I
I'm not sure what links would be, just a page that includes its target stucture?
don't think that there would be a win if they
would be merged. Copying
and moving is something very different.
What if the command arguments were presented as a sentence with
pre-filled holes instead of a key-value table?
E.g. [move/copy] this structure to [./my-current-page-copy ]
But indeed, if you want to have template pages, it would be nice to
block move and edit for standard users, and only allow them to copy
it.
- The split between edit and settings is somehow
arbitrary, but it
makes perfectly sense if you are not the only one editing the site.
Would it be possible to have a composite command that presents the
three interfaces (filtered according to rights) in one page, then
applies the individual commands? Pushed to the extreme, that would
allow per-property accessor commands at the security/persistency
level, grouped by whatever makes sense at the user level…
--
Damien Pollet
type less, do more [ | ] http://people.untyped.org/damien.pollet