Development:Coding
This page is the top-level page describing Moodle's coding guidelines. It's the place to start if you want to know how to write code for Moodle.
WARNING: Under construction RIGHT NOW!
Moodle architecture
Moodle tries to run on the widest possible range of platforms, for the widest possible number of people, while remaining easy to install, use, upgrade and integrate with other systems.
For more about this, see: Moodle architecture.
Plugins
Moodle has a general philosophy of modularity. There are over 25 different types of plugins, however many of these plugin types work the same way.
For more about the structure of plugins, see Moodle plugins.
Coding style
Consistent coding style is important in any development project, and particularly so when many developers are involved. A standard style helps to ensure that the code is easier to read and understand, which helps overall quality.
Writing your code in this way will ensure your code is an important step to having your code accepted by the Moodle community.
Our Moodle coding style document explains this standard.
Security
Security is about protecting the interests and data of all our users. Moodle may not be banking software, but it is still protecting a lot of sensitive and important data such as private discussions and grades from outside eyes (or student hackers!) as well as protecting our users from spammers and other internet predators.
It's also a script running on people's servers, so Moodle needs to be a responsible Internet citizen and not introduce vulnerabilities that could allow crackers to gain unlawful access to the server it runs on.
Any single script (in Moodle core or a third party module) can introduce a vulnerability to thousands of sites, so it's important that all developers strictly follow our Moodle security guidelines.
XHTML
It's important that Moodle produces strict, well-formed XHTML code, compliant with all common accessibility guidelines (such as W3C WAG).
This helps consistency across browsers in a nicely-degrading way (especially those using non-visual or mobile browsers), as well as improving life for theme designers.
Full information is here: Moodle XHTML
Javascript
In general, everything in Moodle should work with Javascript turned off in your browser. If you do have Javascript enabled it should only improve usability (not add features).
This is important for accessibility, and in line with the principles of unobtrusive Javascript and progressive enhancement.
See the guidelines for: Moodle Javascript
Internationalisation
Moodle works in over 75 languages because we pay great attention to keeping the language strings and locale information separate from the code, in language packs.
The default language for all code and documentation, however, is English (AU).
Full details: Moodle Internationalisation
Accessibility
Moodle should work well for the widest possible range of people.
See: Moodle Accessibility
Usability
See: Moodle Interface Guidelines (being rewritten 2009)
Database
Moodle has a powerful database abstraction layer that we wrote ourselves, called XMLDB. This lets the same Moodle code work on MySQL, PostgreSQL, Oracle and MSSQL.
We have tools and API for defining and modifying tables as well as methods for getting data in and out of the database.
Unit tests
Unit testing is not simply a technique but a philosophy of software development.
The idea is to create automatable tests for each bit of functionality that you are developing (at the same time you are developing it). This not only helps everyone later test that the software works, but helps the development itself, because it forces you to work in a modular way with very clearly defined structures and goals.
Moodle uses a library called simpletest (not very extensively yet though!) that makes writing unit tests fairly simple. Our unit testing is currently not deep but we want to improve this.
Full information here: Moodle Unit Tests
