urs_hunkler c24a1ccd08 I added all code to handle the cookies and the sideblock content, the icon and the patches for hiding/showing the content of the sideblocks.
How it works:
_ within the "sideblockheading" a DIV with class="hide-show" holds a link calling the JS containerDisplaySwitching(). To the user it's represented by the icon "switch.gif" (a plus in a square) at the right end side of the header.
_ all content of the sideblock is surounded by a new <div class="blockcontent" id="'.$attributes['id']."_cont\">"
_ a call of the JS containerDisplaySwitching() changes the state of the appropriate DIV with the content to "display:none/inline" and writes this state into a cookie.
_ at the end of every block I added a call to the JS "containerDisplaySet()". This reads the block's state and hides the content or leaves it visible with every page load.
_ in the stylesheet I added the positioning of the icon:
.sideblockheading .hide-show {
    float:right;
}
.sideblockheading a img.hide-show-image {
    padding-top:0.25em;
}
2005-02-05 21:37:53 +00:00
..
2005-01-25 13:17:15 +00:00
2005-01-25 13:17:15 +00:00
2005-01-25 13:17:15 +00:00
2005-01-31 05:58:03 +00:00

<h3>STANDARD THEME</h3>
<hr />

<p>Moodle's default theme is a very neutral grey/white theme.</p>

<p>This theme is always the most up-to date.</p>

<p>Programmers working on Moodle should always design for this 
theme, and add new styles to this theme.</p>

<p>By default, these styles are automatically loaded before any other
themes, so that all custom themes need to do is to define their
own styles to augment or overwrite particular standard styles.</p>

<p>In this way custom themes are not "left behind" by Moodle upgrades.</p>