Martin Dougiamas

Deleted.   Can't wait for 1.7 and the ability to block users from blogs (via Roles). 

Well, it's looking like YUI is the winner, yes?

Let's proceed with that and see how it goes.

Janne, can you post instructions for enabling tinymce in 1.6?  

You skyped them to me once but I've lost them and have no time to look through code anymore. 

TinyMCE is already in 1.6 actually, just disabled.  Janne and I were fully planning to replace HTMLarea in 1.6 but just could not get the performance to anything comparable without major work.  "Tiny" MCE is huge and slow by default.

For Quickform, I think we just need to tackle low-hanging fruit first, like the forms for adding new activity modules, then move on to other areas one at a time.  We don't have to use all the features in Quickform, but just moving to a consistent renderer will be a great first step.

That does look pretty nice, but to me even XML seems to be too complicated.   PHP developers can most efficiently use PHP to create data structures, we don't need to translate them to XML.

The approach I've been planning for a long time (and hoping to include in the upcoming accessibility work) is to use a library to convert PHP data structures into HTML.

There are several of these, but the most likely contender is HTML Quickform, because it's part of PEAR, is mature, extensible, accessible, and supports client and server-side validation, multi-page forms etc. It's more standard than most, and widely used among PHP developers.