|
[
Permalink
| « Hide
]
Martin Dougiamas added a comment - 24/Sep/07 12:25 PM
At a glance, this seems like a good idea. I need to think a bit more about it though ... there might be better ways to do this, such as through extra fields in the access.php files ...
I think an optional function in lib.php makes sense. Let me explain my thinking.
I think it makes sense to make capabilities at the module context level dependent on the module, this will reduce the clutter of irrelevant capabilities being displayed at the module context level. And if what capabilities are displayed in the UI at module context level are dependent on the module, then there must be a way in the module api for the module author to tell Moodle what extra capabilities are relevant for THIS module. As said in HQ chat...
+1 for this idea (being able to specify relevant capabilities for contexts not belonging to them). Current patch looks safe (and sure Petr's one will be). -0.5 for being too much revolutionary in 19_STABLE Ciao the idea is to combine several patches for roles UI changes, set up demo site, ask MD for confirmation, rework, demo, confirmation, cvs and then big celebrations
I wonder what happened about this idea to overhaul the roles UI? I linked an issue to this one - we have introduced db/ sub folders for quiz reports. And they can include access.php files, but some work needs to be done on the UI to get them to display properly in the roles UI.
I have proposed a fix for problems in the linked bug. See that bug for details. hello, I doubt this will be part of 1.9.x
The quiz report db folders will only be available from 2.0. I wonder if something will be done on this in 2.0 and / or whether I should use the patch in
The file/repo API work started today, I hope I will be able to work on all role/enrolment related stuff after this. (2 months from now?)
sending patch with something like this implemented + changed a lot of context levels in cap definitions and improved sorting of caps
should be fixed in cvs
please test toto: document in coding guide somewhere
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||