Forumindlæg af Martin Dougiamas

Billede af Core developers Billede af Documentation writers Billede af Moodle HQ Billede af Plugin developers Billede af Testers

I totally agree.  I reported this issue too just a day before.

MDL-57001

It's a little involved to get right without affecting other themes etc  

We were trying to decide today whether it should hold up the 3.2 release or not and the consensus was probably not, but it should be in 3.2.1 at latest. 

What do you think?   Is this feature useful a lot by teachers?

Billede af Core developers Billede af Documentation writers Billede af Moodle HQ Billede af Plugin developers Billede af Testers
Thanks Damyon and hi all.  I'll be leading the meeting from the Francophone Moodlemoot in Sierre, Switzerland where I am at the moment.


I don't expect that we're going to get a lot DONE at this meeting itself, but I did want to get some of the interested parties together so we can hear each other, agree on the parameters and start to work out what's going to happen over the next few months before the freeze for Moodle 3.2.

This document is the starting point.  

Some of it is about theme infrastructure in general, but some of it is about required core changes to navigational elements, but the most important part of it for me is that we have a new default theme that provides a superior out-of-the-box experience for 3.2 and later, so I hope we can all pull together to make this a reality.

I know a lot of you have worked on some amazing themes for Moodle.  This one can not hit every one of the goals that those have strived for.  But it should be a huge step forward that raises the baseline of what we expect in Moodle's interface.

Gennemsnitsbedømmelse:Useful (2)
Billede af Core developers Billede af Documentation writers Billede af Moodle HQ Billede af Plugin developers Billede af Testers

Progress bar functionality will be integrated into the dashboard, yes, it's part of the new changes commissioned by the Moodle Users Association in the last round:  see MUA-26  

There is still a block region for other things that you might find necessary, however there are no plans to bring blocks to the mobile app EXCEPT on a dashboard page there.

Moodle in English -> Future major features -> Boost theme in 3.2

ved Martin Dougiamas -
Billede af Core developers Billede af Documentation writers Billede af Moodle HQ Billede af Plugin developers Billede af Testers

Rocket imageFollowing from the discussion New theme in Moodle 3.2 I wanted to point out the Bootstrap 4 theme in core is called "Boost" and you can get a taste of it on the prototype site.

Apart from the very significant stuff going on under the hood with respect to the frameworks, you'll notice a number of basic new concepts in the UI:

  • Reduced reliance on blocks.  Navigation and Settings blocks can be deleted completely (and would be in vanilla install).  There is still a block region over on the right if you really need it for critical content (but we advise trying to avoid them, because remember, these don't show on the Mobile app).
  • New "Flat nav" menu on the left with key navigation points (designed to converge with the main menu of Moodle Mobile over time).
  • "Gear icons" on Site, Course, Activity and User pages with a drop down menu that presents the key things from the old Settings block.

If, as a themer, you don't like these, you can easily override them in any child theme and still benefit totally from Bootstrap 4, but I am pushing for these UI features as defaults in Boost to give Moodle a refreshed and modern default appearance that feels more like the many web and mobile interfaces around us, and to raise the baseline for themers.

Any help we can get from you in polishing this concept to make it good enough to be default in our 3.2 release (slated for late November) would be very welcome.

Gennemsnitsbedømmelse:Useful (4)
Billede af Core developers Billede af Documentation writers Billede af Moodle HQ Billede af Plugin developers Billede af Testers

Randy, you're what we might call a power user.  I think there might be other ways to do what you need without resorting t text-only search results.   For example you can make a list of your favourite plugins.  

Can you describe exactly what kinds of tasks you do that require frequent searching?