Urs Hunkler

Good idea to handle the section blocks the same way. I've thought about making the admin pages clearer by showing the helptext only on demand.

Gustav, which blocks are supposed to show without a header? Could there be a reason connected to their task to not hide them?

Your proposal could be realized by introducing a new zone at top of the block content to hold for example a line. A click onto this line would hide the content up to that line. But for the moment I think using the top aerea of the blocks as a handle is more straightforward.

Hi,

I've added the switch to hide/show the content area of the sideblocks to Moodle 1.5 Dev. Please test this functionality - does it work on all systems? Do you notice any speed changes?

With Moodle 1.5 supporting multiple instances of the sideblocks identifying of those instances must be added. In the moment it's like in a spooky hause. When you try to close this window, the other is shut. Does anybody have an idea how the unique identification can be managed?

Hi Gustav,

You write "I don't think the tables in the developer wiki listing all the classes that have been defined on the various pages are so important, after all this information can always be obtained from the page source or, much more conveniently, by viewing a page in firefox with the web developer toolbar."

Do you think a consistent naming scheme will be possible without a root, where everybody can access the information and choose the same names? I'm not shure if looking at the code or the pages with firefox will suffice.

You write "I think page authors need some guidance."
What guidance would you prefer to have? Some informations I can think off could be:

• Documented page examples?
• Explanations how CSS influences the look of some Moodle pages?
• Guidelines for the page design with the needed IDs and CLASSes?

Urs

Gustav, the information in the Developer Wiki has not gone into the details of the single pages. You could start to work on the hooks = CLASSes for the page areas in the quizzes and I can then start the list for the page specific CLASSes and IDs - I've just started with a list with this three classes. So everybody working on the pages can look there and name the objects accordingly.

Can you imagine to lable the page areas with names standing for their task? For example on "quiz/edit.php" the three areas could be named "questions", "categories" and "new-questions". The CLASSes for the table of the left area would be:

<table class="generalbox questions" ...
  <tr>
    <td class="generalboxcontent"> (without the bgcolor tag)
      ...

With the list of CLASSes for the table we can

• either generally address all elements on the page called "generalbox"
• or with the second CLASS "quizzes" the left box individually and not the others on the page

I hope I could help you.
Urs

Hi,

it's looking quit ugly, isn't it ?

yep, the signal means the code should be rewritten without using "$THEME->".

Another way to get fast results would be to change the functions in weblib.php to simply not use the color information and not write them into the html page.

Urs