Martin Dougiamas

In the settings for that image field specify a height OR a width (not both). Your browser should now scale the image without distortion.

Yep, I've been tweaking a lot.

I can see there is some scope for confusion with forums since you arrive at a list of "courses" which contain forums. Several people gave feedback that they preferred "courses" and technically it is accurate. So I changed it back (even though forums is my favorite).

"Courses" has it's own problems of course, since it might help confuse people who were told by their teachers "look for your courses on Moodle" (which seems to happen a bit).

Neither is fully satisfactory. Nor is a whole new term like areas or places.

Any ideas for solving this one? Note that the menu also needs to appear (without dropdown because that is just way too hard right now) on Moodle docs and the tracker and all the other moodle sites.

For years a lot of us have been thinking about a variety of problems to do with the display of Moodle and how bits are put together, including general navigation, blocks, layout and themes. In particular Tim Hunt has been spending a lot of time on this recently for us.

The solutions are not always obvious, and I'd really like to see more of the community engaging with these issues and helping to define the best way forward.

It would be nice to come to some consensus for at least some of these by 2.0, and so with this aim, let's make next week "Navigation, Layout, Blocks, Themes and Other Stuff Week!" (NLBTAOSW - catchy isn't it?)

Your homework starts here on this evolving overview:

http://docs.moodle.org/en/Development:Navigation_2.0

Your assignment next week is to engage in the discussions and vote on proposals as they come up!

The main block class should have an applicable_formats() method like this:

function applicable_formats() {
return array('all' => false, 'my' => true);
}

Apart from different database formats ... you could try and make sure the quizzes are split up into less questions per page ... this will spread out the database accesses into more but smaller chunks.

And obviously you could get more CPU, more RAM, faster disks ...