It's a good question that I don't know the answer to exactly. What do you think?
(1) seems a little strange to do in core, because the whole point of this was about separating the core logic from the display and theme. I suppose a theme could choose to output blocks XHTML differently depending on the "region" they are going into.
Basically I had been thinking (3), perhaps this can easily be done with one common CSS that affects everything inside a given region container.
Something like:
.region#top div.sideblock div.header {
some css to hide headers ...
}
Martin Dougiamas
Posts made by Martin Dougiamas
Since the header and footer printing functions can be completely overridden by each theme, this is totally up to you! 
It probably makes sense to keep these existing templates working by default so that pre-2.0 Moodle Themes don't need so much work to upgrade.
Headers/footers don't have to have much in them, and yes blocks in "top" and "bottom" will be possible most of the time (though they will need custom CSS to make them not look like blocks and place them exactly).
It probably makes sense to keep these existing templates working by default so that pre-2.0 Moodle Themes don't need so much work to upgrade.
Headers/footers don't have to have much in them, and yes blocks in "top" and "bottom" will be possible most of the time (though they will need custom CSS to make them not look like blocks and place them exactly).
I just want to reiterate that now is the time to help with this spec because it's starting soon.
I also want to say that I like the plan the lot - I think it addresses all the concerns that I've ever heard about Moodle navigation and theme design. And it does it in an evolutionary way so there shouldn't be any shocks.
I'm quite looking forward to seeing what site designers and theme designers will be able to do with this!
I also want to say that I like the plan the lot - I think it addresses all the concerns that I've ever heard about Moodle navigation and theme design. And it does it in an evolutionary way so there shouldn't be any shocks.
I'm quite looking forward to seeing what site designers and theme designers will be able to do with this!
If the module is something useful on its own, and the other code X is something absolutely completely separate and underived from Moodle that simply adds some value when it is installed, then I think that's probably OK to sell X under a different license. it's not great but it's probably allowed.
Otherwise, if the two parts are dependent then you really aren't "giving the module away for free", are you? The module won't achieve its main purpose without the libraries so it'd be pure marketing spin to describe it as free.
What you are really doing there is distributing GPL code mixed with non-GPL code. Which you definitely can't do.
See: http://www.gnu.org/licenses/gpl-faq.html#MoneyGuzzlerInc
Otherwise, if the two parts are dependent then you really aren't "giving the module away for free", are you? The module won't achieve its main purpose without the libraries so it'd be pure marketing spin to describe it as free.
What you are really doing there is distributing GPL code mixed with non-GPL code. Which you definitely can't do.
See: http://www.gnu.org/licenses/gpl-faq.html#MoneyGuzzlerInc
Hi,
This should not be posted to the public forums.
It was posted to Moodle admins privately for a reason (which was to give everyone a chance to upgrade before it went public)
We obviously need to come up with some way of translating these emails though!
This should not be posted to the public forums.
It was posted to Moodle admins privately for a reason (which was to give everyone a chance to upgrade before it went public)
We obviously need to come up with some way of translating these emails though!