Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

Developer meeting April 2015: Difference between revisions

From MoodleDocs
(The maths pedant strike ;-))
Line 49: Line 49:
* by [https://moodle.org/user/profile.php?id=12863 Petr Škoda] (confirmed)
* by [https://moodle.org/user/profile.php?id=12863 Petr Škoda] (confirmed)
* MDL-49684
* MDL-49684
Moodle 2.9.0 is switching to native PHP date and time code. The old homegrown DST switching routines were completely removed.


=== Per-request temp directories ===
=== Per-request temp directories ===

Revision as of 21:03, 19 April 2015

Developer meetings > April 2015 meeting notes

Time 07:00 UTC on Tuesday, 21 April 2015 Add to my calendar
Meeting room Live stream at YouTube
Forum discussion GDF thread
Chat Regular dev chat
Twitter #moodledev
Event page Google+ event page

Agenda

The meeting focuses on changes in the upcoming Moodle 2.9 release with special attention paid to impact of these changes on community contributors and plugin authors.

Work in progress - individual items to be confirmed, the exact order is subject of change.

Navigation improvements

First experiences with mustache, the new template framework

To see how to work with the Moodle Mustache implementation I refactored the »clean« theme to a Mustache theme. The process went quite well. I'll try to show the main thoughts and steps in the refactoring process in about 10 minutes. We may have some time to talk about Moodle Mustache afterwards.

You may have a look at the theme »cleanm« in my Git repo.

Urs Hunkler (talk) 23:32, 13 April 2015 (AWST)

Unified AJAX script handler

Timezones handling

Moodle 2.9.0 is switching to native PHP date and time code. The old homegrown DST switching routines were completely removed.

Per-request temp directories

Behat tests runs in parallel

As we have over 33000 behat steps in moodle and it's growing rapidly. It takes around 12 hours to execute whole behat suite, which is not expectable for any testing environment. With initial work from Tony and Damyon, we came up with strategy of splitting feature files in different processes and run them in parallel. I will try cover options and demo for running behat in parallel.

More

  • If you have something you'd like to add to this page, please contact David Mudrák.