David Scotson

Actually what you're wanting to do is very much easier than what is done in BootstrapBase/Clean. The way it is in those themes currently with nesting etc. will probably only confuse you. Since you're doing something so much more bootstrappy, rather than Moodley, starting from the Bootstrap docs (http://twitter.github.io/bootstrap/scaffolding.html#gridSystem and search for "fluid grids") is probably easier.

You only need a single row and the three columns would be:

<div class="row-fluid">
   <div class="span6">Main</div>
   <div class="span3">Pre</div>
   <div class="span3">Post</div>
</div>

If you want the block columns to appear and disappear and the main content to vary its width in response then you need to increase the span of the Main section to compensate so it still adds up to 12, depending on how many columns are present in the content:

<div class="row-fluid">
    <div class="span9">Main</div>
    <div class="span3">Pre</div>
</div>

or

<div class="row-fluid">
    <div class="span12">Main</div>
</div>

I'm assuming you can translate that brief overview into PHP. And then you just need to put the PHP code to output the usual block and content stuff in the appropriate place. As a bonus you should get RTL for free with this kind of layout.

A next step that Bootstrap doesn't do by default (yet, I think they're possibly adding it in the next version) but can be done just with some CSS is to make the two block columns collapse into one column at narrow widths (e.g. iPad horizontal and netbooks) but before everything collapses to a single column at iPad vertical size.

I would have much preferred if BootstrapBase/Clean had used exactly this layout, so I'm glad to see someone experimenting with it. If I can help in any way let me know.

I think I've seen the upgrade problem you talk about. I see it all the time but since I'm usually in the middle of an upgrade it's never a good time to be poking about.

I did look into it further once and as far as I could tell the styles.php simply wasn't returning any CSS when called until after that page. And it possibly had something to do with having theme developer mode on.

I think you should be able to partially change this in the renderer function "block_controls":

public function block_controls($controls) {
if (empty($controls)) {
return '';
}
$controlshtml = array();
foreach ($controls as $control) {
$controlshtml[] = html_writer::tag('a',
html_writer::empty_tag('img', array('src' => $this->pix_url($control['icon'])->out(false), 'alt' => $control['caption'])),
array('class' => 'icon ' . $control['class'],'title' => $control['caption'], 'href' => $control['url']));
}
return html_writer::tag('div', implode('', $controlshtml), array('class' => 'commands'));
}

The src will always be something like t/delete or t/move, so you could always add "_block" to the end and then create images called t/delete_block. However, this will only affect the block edit controls, the block hide/show/dock icons are all added by javascript which is (generally) outside the control of renderers. See my other comment about changing them in the javascript.

You can find and change switch_minus/plus in the javascript file 'lib/javascript-static.js' and make the same fix:

https://github.com/ds125v/moodle/blob/master/lib/javascript-static.js

The long term fix for this issue is (in my opinion) the adoption of an icon font created from the current SVG icon.

I started this bug about it if anyone interested in following progress/helping:

https://tracker.moodle.org/browse/MDL-37231

Currently most of the discussion is focussed on the ability to link to any kind of font from a Moodle theme, but I've already experimented with replacing moodle icons with fonts and large areas are fairly easy to do. Perhaps we can get the more difficult bits done in time for 2.6?

It's not a direct solution to this issue but...

If the specific font you are wanting to use (or a close substitute) is available from Googe Web Fonts (or similar) then directly linking to it there rather than providing the files in the theme works, is a bit simpler and provides a few other benefits too (smaller sizes, faster loading, etc.)

Basically, if you can use this service you should, but it also avoids the themedir issue.