Moodle  2.2.1
http://www.collinsharper.com
theme_overridden_renderer_factory Class Reference
Inheritance diagram for theme_overridden_renderer_factory:
Collaboration diagram for theme_overridden_renderer_factory:

Public Member Functions

 __construct (theme_config $theme)
 get_renderer (moodle_page $page, $component, $subtype=null, $target=null)

Protected Attributes

 $prefixes = array()

Detailed Description

This is renderer factory allows themes to override the standard renderers using php code.

It will load any code from theme/mytheme/renderers.php and theme/parenttheme/renderers.php, if then exist. Then whenever you ask for a renderer for 'component', it will create a mytheme_component_renderer or a parenttheme_component_renderer, instead of a component_renderer, if either of those classes exist.

Since:
Moodle 2.0

Definition at line 248 of file outputfactories.php.


Constructor & Destructor Documentation

__construct ( theme_config theme)

Constructor.

Parameters:
object$themethe theme we are rendering for.

Reimplemented from renderer_factory_base.

Definition at line 256 of file outputfactories.php.

Here is the call graph for this function:


Member Function Documentation

get_renderer ( moodle_page page,
component,
subtype = null,
target = null 
)

Implement the subclass method

Parameters:
moodle_page$pagethe page the renderer is outputting content for.
string$componentname such as 'core', 'mod_forum' or 'qtype_multichoice'.
string$subtypeoptional subtype such as 'news' resulting to 'mod_forum_news'
string$targetone of rendering target constants
Returns:
object an object implementing the requested renderer interface.

Implements renderer_factory.

Definition at line 270 of file outputfactories.php.

Here is the call graph for this function:


Field Documentation

$prefixes = array() [protected]

Definition at line 250 of file outputfactories.php.


The documentation for this class was generated from the following file:
 All Data Structures Namespaces Files Functions Variables Enumerations