|
|
| (11 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| {{Moodle 2.0}}
| | #REDIRECT [[:dev:How Moodle outputs HTML]] |
| | |
| If you think about the HTML that is generated by Moodle, then you can split it into two parts: the parts like the header and the user-interface, that are generated automatically by the Moodle code, and the themes; and the bits like the contents of forum posts and labels that are input by the users. This page is about the bits of output that are generated automatically. It explains how that happens.
| |
| | |
| I need to explain the consequences of [[Development:Theme_engines_for_Moodle%3F]], which was a before-development document.
| |
| | |
| The aim should be that people writing core code, plugins or themes can easily find out what they actually have to do.
| |
| | |
| {{stub}}
| |
| Actually, please don't start editing this page yet. I will be working on it as and after I have work on the code.--[[User:Tim Hunt|Tim Hunt]] 03:30, 17 June 2009 (UTC)
| |
| | |
| ==Overview==
| |
| | |
| ==Renderers==
| |
| | |
| ==Themes==
| |
| | |
| $THEME gets initialised the frist time you use $OUTPUT, or the first time you refer to $PAGE->theme
| |
| | |
| ===Basic themes===
| |
| | |
| ===Minor changes to the HTML===
| |
| | |
| ===Templated themes===
| |
| (Experimental)
| |
| | |
| ==Plugins==
| |
| | |
| | |
| ==See also==
| |
| | |
| * [[Development:Theme_engines_for_Moodle%3F]]
| |
| * [[Development:Navigation_2.0_implementation_plan]]
| |
| * [[Development:Navigation_2.0]]
| |
| | |
| {{CategoryDeveloper}}
| |
