Basic group permissions editing functional - enforcing is trivial
add group now adds the permissions entry. TBD: permission inheritance
edit group Does The Right Thing(TM) - either editing the existing entry,
or converting an inherited permission group to a separate one. still
needs to rewrite subgroup and contained user inherited permissions
the HTML permissions table rows have been moved. edit-user should pick
this up, and will require calling the template explicitly so as to show
both the default and custom permissions.
the list of individual permissions have been moved to a list in DNSDB.pm
code that refers to this should not assume any given length - this makes
adding new permission types (somewhat) easier
Tweak menu group-tree CSS (again) add some (broken) images
this should probalby revert to an earlier setup that uses an image
as the <li> bullet point rather than pushing the text to the right,
since many (most?) nodes will usually be leaf nodes