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?
Perfect! This is clean and useful. And, just as importantly, it gives Moodle a modern feel. Now if you could just do the same for the section blocks in the courses please 
.
And by the way: it works fine in Firefox, IE6 and Opera7 under Windows XP. In Firefox the bottom round corners disappear when the box is collapsed, but that doesn't bother me too much.
One slight problem is that blocks that are not supposed to have a title bar acquire one due to the little icon. Is there something you could do about that, like put the icon into the content instead of the header?
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.
The two blocks that I know make use of the possibility of having no title are course_summary and html.
One easy way to avoid the problem would be to just not use your new feature on blocks that don't show a title.
Hi Jon,
onclick="..." (I was wondering, why was it done this way?)
I'm not a programer, you know . I found several actual and good websites (design websites) doing the show/hide of informationchunks on webpages this way, so there was no reason to do it different. What would be the advantage of using "onclick" instead of "a href"?
and then detect which element the click happened on and set its display properties accordingly.
If I understand you right, you propose something different. As shown in the figure below there are two DIVs, the header and the content. Within the header the user can activate the "switch". The fast and secure way is to activate a JavaScript with the content's ID as a parameter to hide/show this object. As I understand your proposal you want to hide the triggered object itself - I don't see a chance to show the hidden block, when the header is gone too
Using the whole header as the clickzone does not work, because the header would catch all events and would disable the edit buttons of the blocks in edit mode.
.hidden .sideblockheading {
color: #999 !important; /* gray */
}.hidden .sideblockmain {
display: none !important;
}.sideblock .hide-show img {
height: 16px;
width: 16px;
background-image: /* a "hide" icon */
}
.hidden .hide-show img {
background-image: /* a "show" icon */ !important;
}Jon,
thank you very much for your great changes you proposed and you made. It's so much more elegant and flexible than the first version.
PS: On test.moodle.com I saw the two instances of the RSS block close and open as expected. But after a page reload they are both displayed in the same state even if the user had them displayed differently (the state of the last switched block).