Patrick Malley

I have about 10 designs right now that are ready to code for 2.0. I also have a small handful of people waiting for documentation to create themes themselves. I'd then ideally like to create some 2.0 themes that show it's full set of capabilities. Doing this will require some pretty solid documentation.

Essentially, I've committed myself to creating a lot of themes and I'm concerned that I won't be able to deliver as promised if the themes engine is not nailed down sooner than later.

That's a bit of a panicky statement, I realize. I appreciate all that has been done and do not mean to gripe. I'm simply concerned that I won't have enough time to get these themes together for a 2.0 beta release.

Specifically, I need

- one theme in the core that is considered beta to use as a template.
- theme documentation explaining the full capabilities to non-programmers like me.
- two to three months to play around and code.

I'm trying to use file_exists to have Moodle check for a logo file in the theme folder. Unfortunately, it's not working. Here's what I have $filename= "$CFG->themewww/accentuate/images/logo.jpg"; if (file_exists($filename)) { I'm guessing that the problem is in the way I'm passing the $filename variable through file_exists. Any help is appreciated.

I've just released two simple new themes for Moodle: Greenie & Leatherbound. Both are free and open source. Please post any support requests and feedback here.

Enjoy.

As part of the 2.0 release, I'm working on finding and creating 20 new themes to include in the Moodle core. It's been mentioned that we ought to also drop the Standard theme variants (Standard Red, Standard Blue, Standard Red, and Standard Logo) as they really don't add much to the Standard theme (approximately 12 lines of CSS in each) and they'd look pretty plain alongside the others we'll be adding.

So, what do we do with these variants?

1.) We could completely get rid of them.

2.) We could put the alternatively colored stylesheets inside Standard as I've done for Nonzero and Ingenuous and let people decide whether or not to use them themselves.

3.) We could leave them as individual themes as they exist now.

- I like the idea of the second option, but it does clutter up the Standard theme beyond it's purpose.

I'm very interested in everyone's feedback on this.

I'm happy to announce this new theme for inclusion in 2.0 - I've coded it for testing on Moodle 1.9 and you are free to download it here.

It includes four color variants and a single-level menu bar. Please report any bugs that you find in the tracker and post any questions you have here.