Urs Hunkler

Sorry 2) may be not clear. It should read:

2) possible to override the headingmenu output when it is output via a renderer via $OUTPUT.

Some questions:

Moodle 2.0 is prepared for the page layout "admin". Another type of administrational pages are the settings pages - like course settings.

Please add the page layout type "settings" to the page layout list.

With "admin" and "settings" pages clearly defined it will be easy to create page designs optimized for administrational tasks. The demands for administrational pages are quite different from course or module/resource pages.

Some questions:

How is a module supposed to set up and use module page renderers?

Tim mentioned that there will be at least one example module to show how modules may be build using renderers (the forum module for example). I would appreciate such an example to be close to Moodle core with module development.

Some questions:

When I get the role of $PAGE and $OUTPUT right, $PAGE holds information, $OUTPUT is used to render the information for output. Right?

In 'base/layout/frontpage.php' I see echo $OUTPUT->lang_menu(); and echo $PAGE->headingmenu; This looks inconsequent - I would expect the second statement to be echo $OUTPUT->heading_menu(); Why are the two menus output differently?

As I think it would be
1) easier to keep an overview when checking for content would be done via $PAGE and the output always rendered via $OUTPUT.
2) impossible to override the headingmenu output because it doesn't use a renderer.

Some questions:

Is there an easier/better way to get an overview of the variables and function calls available in the layout scripts than reading the code? I hope here is, because with $OUTPUT, $PAGE, $PAGE->theme etc. there is a lot of code to check in quite different places.