To make the work of plugin developers on mobile easier, Moodle HQ has released a charter. Named “Mobile support for plugins,” it is intended to organize ideas and showcase progress.
Ever since the release of Moodle 3.1, developers were technically able to extend plugin functionality to mobile devices. On mobile, plugins are called “remote add-ons.” Making a plugin compatible with Moodle’s apps is difficult and lacking in standards. Installation requires manipulation of the core code in most cases.
The solution to these problems already exists, at least for the most part, in the architecture of plugins. As the document explains, the specification for mobile add-ons must fulfill the following:
- Easy to build, maintain, install, and update.
- Support Moodle 3.1 and newer.
- Support all types of plugins, operating systems, and devices.
To date, the document outlines the general plan that would enable this and make Moodle Mobile compatible with plugins:
- A plugin will now include and additional mobile.php file that would list the level of mobile support by each feature.
- For new or modified functions, new code must be added. It will be referenced following a series of rules that would let the system identify it so they are accessed according to each case.
- It would require a “basic markup” of Ionic that would enable modular development.
The document is available here. It features a practical example of the modifications made on a plugin files folder.
Reach out to Moodle HQ Developers on Twitter @moodledev.
This Moodle Technology related post is made possible by: Moonami a company that provides a full range of Moodle services that combine the flexibility, scalability, and power of Amazon’s world-leading cloud platform (AWS) with fanatical Moodle support. Click here to learn more.