mirror of
https://github.com/moodle/moodle.git
synced 2025-02-13 20:36:42 +01:00
d4a03c00ea
The code to print blocks in now in theme layout.php files. (Or in moodle_core_renderer::handle_legacy_theme) Code for printing blocks everywhere else has been stripped out. (Total diffstat 1225 insertions, 2019 deletions) The way the HTML for a block instance is generated has been cleaned up a lot. Now, the block_instance generates a block_contents object which gives a structured representation of the block, and then $OUTPUT->block builds all the HTML from that. How theme config.php files specify the layout template and block regions by page general type has been changed to be even more flexible. Further refinement for how the theme and block code gets initialised. Ability for scrits to add 'pretend blocks' to the page. That is, things that look like blocks, but are not normal block_instances. (Like the add a new block UI.) Things that are still broken: * some pages in lesson, quiz and resource. I'm working on it. * lots of developer debug notices pointing out things that need to be updated.
<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>