Martin Dougiamas

It nearly is. It would be better to use/wait for it than to hack 1.6, believe me.

> using template to decide what to be shown to users and what not.

We have that too in 1.7, it's called Roles.

Frankly, I can't see too many cases where this would be useful.

We already have this:

1. lib/weblib.php, which should be used by all modules to produce page parts. Really it's just a collection of little php templates already. Modules-makers SHOULD be using these functions all the time, yet often they don't.
   
2. Lots of tables converted to divs only.

We are already working on this:

1. Removing remaining tables used for layout (1.8)
2. Formatting output using clean XHTML and sensible CSS hooks (1.5 ongoing)
3. Converting all forms (the major part of the interface) to be consistently produced by a new core Moodleforms library based on HTML Quickform (lib/formslib.php) (1.8)

I think this is enough. That's what XHTML + CSS is supposed to be designed for (by designers!!!).

What we could do is somehow allow themes to replace weblib.php with their own functions, but as I said, I can't see how useful that would really be. I'm a little wary of spending a great deal of time on something that only a very small proportion of Moodle users would find useful.

I'm a little disappointed in how few themes are really pushing the envelope of what I know is already possible even in Moodle 1.5 (think csszengarden-type overhauls)

Should you wish to listen to that interview, it's .

And here is a page with all the interviews.

As you can see, we don't really have time to develop/maintain a repository, especially one with an ever-growing list of features people demand of it.

So the whole direction at the moment is to implement a Repository API in Moodle that all developers talk to, and use external repository systems to actually handle the files. In the long run this is a lot better, because often people have existing systems they want to plug-in to Moodle.

I expect to see this in Moodle 1.9 for sure.

Background: RFC ::: Open University Repository System Proposal