Note: You are currently viewing documentation for Moodle 2.3. Up-to-date documentation for the latest stable version is available here: How Moodle outputs HTML.

Obsolete:How Moodle outputs HTML: Difference between revisions

From MoodleDocs
m (→‎Themes: added an information that sounds important to me)
No edit summary
Line 1: Line 1:
{{Moodle 2.0}}
{{Moodle 2.0}}


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.
If you think about the HTML that is output 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.
{{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)
 
 
==History==
 
Most of what is described here is new in Moodle 2.0. The work that lead to this new system is described in [[Development:Theme engines for Moodle?]] and [[Development:Navigation 2.0 implementation plan]]. Those documents were both written before the new system was developed and shows how the thinking evolved.


The aim should be that people writing core code, plugins or themes can easily find out what they actually have to do.
If you are familiar with Moodle 1.9 or before, and just wish to update your existing code, you may wish to read [[Development:Migrating your code to the 2.0 rendering API]].


{{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==
==Overview==


==Renderers==
==Renderers==

Revision as of 13:29, 10 July 2009

Template:Moodle 2.0

If you think about the HTML that is output by Moodle, then you can split it into two parts:

  1. the parts like the header and the user-interface, that are generated automatically by the Moodle code and the themes; and
  2. 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.

Actually, please don't start editing this page yet. I will be working on it as and after I have work on the code.--Tim Hunt 03:30, 17 June 2009 (UTC)


History

Most of what is described here is new in Moodle 2.0. The work that lead to this new system is described in Development:Theme engines for Moodle? and Development:Navigation 2.0 implementation plan. Those documents were both written before the new system was developed and shows how the thinking evolved.

If you are familiar with Moodle 1.9 or before, and just wish to update your existing code, you may wish to read Development:Migrating your code to the 2.0 rendering API.


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

Template:CategoryDeveloper