Urs Hunkler

For who may not be pleased by the Moodle CSS file structure: in the new ALA article "Progressive Enhancement with CSS" http://www.alistapart.com/articles/progressiveenhancementwithcss a very similar solution is described.

The Moodle CSS separation solution is quite up to date

The Moodle-AMF integration should be as open as possible. Not only focus on AMFPHP but also on Weborb and probably Sabre.

I for example switched from AMFPHP to Weborb because Weborb offers messaging.

An approach focusing on Moodle-AMF and being open for the technology (as Jamie already mentioned) to implement it depending on the project needs has more chances for success.

Ok Guy. You always need to see the whole picture (needs for the special page) and decide if fast page load impression or enhanced functionality weights more.

Or create a solution in between when necessary. And therefore we need the most flexible way to make the best solution possible.

Marvellous Tim - looking forward to work with the comfortable and fast JS integration in Moodle.

And please don't forget to make it easy to integrate other JS libraries than YUI. Thank you.

Guy, may you have a special understanding of "unobtrusive JavaScript"?

You write about links not working when JS is loaded in the footer. What happens when you don't have JS at all?

The ALA article "Understanding Progressive Enhancement" http://www.alistapart.com/articles/understandingprogressiveenhancement explains the content/presentation/interaction layers nicely.

The interaction layer (JavaScript) enhances user experience but must not break the page when it's not present. The page works without JS.

@ JavaScript before the page is ready loaded.
When pages need JS before the page is ready loaded I propose to use highly optimized JavaScript and not use one of the huge JS libraries. And YUI is a really big one. This JS may either be included into the page or be loaded from the header.