David Scotson

The root of the issue is that it's not actually "in" the "container", it's floated over the top to look like it is because a hacky CSS solution was, at the time, more acceptable than a hacky renderer solution, or a proper renderer solution.

To continue the CSS hackery you could just make the button thinner (or use a smaller preset button size) or make the navbar bigger.

There's probably lots of interesting options for what you can do with that button, but currently the bit of code that puts the button there also does a random handful of unrelated things that all get dumped in the same place depending on what screen you're on (I think each page basically gets to decide what to put there, but I might be wrong). If that was teased apart your options would expand greatly but I'm not sure that's possible.

I'd probably lean towards a slightly hacky renderer solution that inserts the button renderer into the output of the navbar renderer.

Looks quite nice. I particularly like the font and having the wide range of font widths opens up some interesting possibilities..

http://www.latofonts.com/lato-free-fonts/

http://www.google.com/fonts/specimen/Lato

Like Bootstrap 3 the Moodle theme needs a little bit of tweaking to make the turn editing on button fit where it currently is because the buttons are bigger.

Someone should really start a project to port all the Bootswatches to Moodle Themes so that the little things like that can be worked on collectively and sorted once and for all.

There's a new Bootswatch based on the popular Flat look that's been all the rage lately:

http://bootswatch.com/flatly/

(Original inspiration http://designmodo.github.io/Flat-UI/ )

Thought I'd mention it as some people have expressed interest in the Flat UI, but it's use of SASS made it a bit tricker to integrate into Moodle (on reading further it seems the pro version of Flat UI that you have to pay for added a LESS version).

I guess my main worry was that they were appearing on quite a few things that I wasn't expecting YUI javascript to be touching in any way. And if they are added by javascript after page load (which it appears they are) then this might be visible to the end user as a delay in the page being ready if they are accidentally being added to too wide a target.

Having said that, I can't actually find any right now (looked in this page, the Theme forum page, the Using Moodle page) so perhaps when I was seeing them everywhere there was something broken, but it was just on my particular system at that point, perhaps due to me mucking around with themes.

That's really great info Tim, thanks. I'll have a go porting some of the stuff I've just done as simple classes to this format, inside a theme at renderer (or two) first.