My comment was directed to you only in the sense that you're scaring people away from excellent, useful themes like Essential and Clean for no good reason.
These themes, like all themes, and like Moodle itself, have bugs. People report these bugs because they're excited about using the themes, and people seem quite excited about Essential right now so perhaps you've been misled into thinking that it has more bugs than other themes, when really it's just got more people interested in using it?
It seems like every bug report for Essential starts with "Wow, great theme, there's just one little thing...". Maybe they're just being polite but I think it's more likely that they really think it's a great theme and just want to report the little problem they've found, or offer a suggestion for improvement, because Julian has been so good at responding to people's feedback.
Similarly, many of the Clean bugs are things that have never worked in Moodle, but since themes generally didn't work on mobile devices nobody had bothered to check if e.g. PDFs you drag'n'drop into Moodle can be viewed on iPads. Scaring people away from Clean and Essential is not going to get those Moodle bugs fixed (or found and fixed) any faster.
David Scotson
Oqallisissiat David Scotson-imit allatat
And, I take offense to that comment.
There's issues with Clean theme, though mostly core Moodle bugs that people seem strangely reluctant to fix, but it's still better than most other alternatives, doubly so if you expect users to use iPhone, iPads or other mobile devices.
The fact that Moodle's own MOOC is running with a variation of Clean should be some indication of how ready it is, and people have been running variations of it in production since 2.3.
There's issues with Clean theme, though mostly core Moodle bugs that people seem strangely reluctant to fix, but it's still better than most other alternatives, doubly so if you expect users to use iPhone, iPads or other mobile devices.
The fact that Moodle's own MOOC is running with a variation of Clean should be some indication of how ready it is, and people have been running variations of it in production since 2.3.
From the other screenshot I'd guess that they're using a table to layout the "Required Configuration" info and it's quite likely that it says somewhere "this table should be 1000px wide" or similar.
edit: actually re-reading the issue it seems they can't move the TOC block. Is it really possible to move that block in Clean and Standard? It's not obvious to me how you do it if it is possible.
edit: actually re-reading the issue it seems they can't move the TOC block. Is it really possible to move that block in Clean and Standard? It's not obvious to me how you do it if it is possible.
You might want to comment on the bug CONTRIB-4557 or open a new one about the ddmarker, as they were fairly responsive the last time. It's not an Essential problem, it'll affect any theme that inherits from Clean (and any that otherwise try to make img's resize for mobile devices in the same way.)
They may have to rethink their strategy if they want the question type to work on mobile devices though. I'm not sure how a question with a near lifesize desktop screenshot is ever going to work on an iPhone.
They may have to rethink their strategy if they want the question type to work on mobile devices though. I'm not sure how a question with a near lifesize desktop screenshot is ever going to work on an iPhone.
I think that's mostly a core Moodle bug / design decision, though there is something weird going on.
The move arrow that lets you move blocks without dragging (you click the block you want to move, then click where you want it to go) is supposed to disappear when javascript is active in favour of drag'n'drop. Instead you're supposed to just know that you can drag blocks and grab them somewhere around the title.
I'd guess in this case something is breaking the javascript in the center column to stop it removing that icon and perhaps also stopping it being used as a drop-target for blocks coming from the sides. This is very easy to do if you rename a class in a div that surrounds the target of the javascript.
(Interestingly this all seems to be broken on the very latest core Moodle in development, qa.moodle.net is showing a similar issue but the icon remains everywhere).
The move arrow that lets you move blocks without dragging (you click the block you want to move, then click where you want it to go) is supposed to disappear when javascript is active in favour of drag'n'drop. Instead you're supposed to just know that you can drag blocks and grab them somewhere around the title.
I'd guess in this case something is breaking the javascript in the center column to stop it removing that icon and perhaps also stopping it being used as a drop-target for blocks coming from the sides. This is very easy to do if you rename a class in a div that surrounds the target of the javascript.
(Interestingly this all seems to be broken on the very latest core Moodle in development, qa.moodle.net is showing a similar issue but the icon remains everywhere).