Development:Developer documentation

Note: New developer documentation pages should be added to the Development namespace by typing Development: before the new page name i.e. [[Development:New page name]].

If you are a developer, you probably want to change your preferences to include the Development namespace in searches.

A page may be added to the Developer category by typing [[Category:Developer|New page name]] at the bottom of the page.

How Moodle development works

This overview of the Moodle development process may be handy in understanding how the development of Moodle occurs and how people become Moodle developers.

Guidelines

The following guidelines are crucial reading for anyone wanting to contribute to the Moodle code base:

• Coding guidelines have to be followed by all Moodle developers
• Moodle design goals spells out the basic design goals behind Moodle
• Interface guidelines aim to provide a common feel to the Moodle user interface
• Moodle CVS for developers explains how to work with the Moodle code in CVS
• Tracker explains the Moodle Tracker for keeping track of bugs, issues, feature requests etc
• Working with the Community explains how to engage with the dev community and discuss changes
• Unit tests explains how to run the unit tests, and how to write new test cases.

Documentation for core components

This section is for documentation of specific components of the existing core Moodle code. Discussion of components that are under discussion or in development can be found in the Developer notes or on the Roadmap.

The documents below give a general overview. For detailed function-by-function documentation, see the phpDocumentor documentation that is automatically generated from the comments in the code. And don't forget that the most up-to-date and detailed description of how the code works is the code itself. Moodle code should be easy to read and understand. Use the source, Luke!

Core components that affect everything

• lib/moodlelib.php
• lib/weblib.php for outputting stuff.
• Database abstraction layer @ v1.7
• Roles and Capabilities system @ v1.7 for controlling who can do what.
• Forms library @ v1.8 for creating accessible and secure HTML forms that let users edit things.

Core libraries with a more specific uses

• Authentication API
• Cookieless Sessions
• Moodle Network
• Email processing
• Environment checking before install, check the user's server to ensure Moodle will work there.
• Question engine
• Stats package
• Migration to UTF-8 @ v1.6
• YUI JavaScript library - YUI was selected as the official AJAX library for Moodle.

Modules included in the standard distribution

• Quiz module
• SCORM module 1.5 schema

How you can contribute

Make a new plugin

The M in Moodle stands for modular, and the easiest, most maintainable way to add new functionality to Moodle is by using one of the many plugin APIs. There are many types of plugin you can write:

• Activity modules
• Admin reports
• Assignment types
• Authentication plugins
• Blocks
• Course formats
• Course reports
• Database fields
• Database presets
• Enrolment plugins
• Filters
• Grade export/import
• Grade report
• Question engine
• Question import/export formats
• Quiz reports
• Resource types
• SSO plugins
• Course Report Plugins

When you have developed a new component please publish it in the Moodle modules and plugins database.

Change core code

Some types of change can only be made by editing the core Moodle code. Such changes are much harder to maintain than plugins. If you want your core change to be considered for inclusion in the official Moodle release, you need to create an issue in the tracker, and attach your change as a patch. It is also a good idea to discuss your ideas in the forums first.

Ways to contribute that do not involve PHP programming

• Create Moodle themes
• Translate Moodle into other languages
• Help document Moodle
• Database schemas
• Join the testing effort, which involves participating in the bug tracker

Plans for the future

Ideas for and details of planned future features of Moodle are initially discussed on the forums in the Using Moodle course at moodle.org. That developer discussions are intermixed with user discussions in the same forums may seem strange at first but is one of the reasons for the success of Moodle. It is important that both end-users and developers discuss the future features together.

Once ideas begin to crystallize on the forums they can be summarized in this wiki, either as part of the Roadmap or in the form of Developer notes. These pages then form the basis for further discussion in the forums.

• Roadmap
• Developer notes
• Student projects
• Developer conferences

Resources and tools

• Developer FAQ - frequently asked questions, especially useful for newcomers to Moodle
• Finding your way into the Moodle code - also aimed at newcomers
• Moodle tracker - bug reports, feature requests and other tracked issues
  • Firefox tracker search - How to setup a firefox quicksearch to easily navigate to moodle bugs
• Unmerged files - changes on the stable branch in CVS that have not been merged to HEAD
• Browse the code online:
  • the code with a complete change history from CVS
  • the code, with links generated by PHPXref
• Moodle PHP doc reference - compiled from the comment attached to each class and function in the code
• Database Schema - for recent releases
• Development news and discussion section of Using Moodle course
  • especially the General developer forum
  • cool tricks you can use in the moodle.org forums
• Some tools people use when working on Moodle code:
  • Setting up Eclipse for Moodle development - Eclipse is a great editor to use for php development, if you can work out how to set it up.
  • Setting up Vim for Moodle development
  • Ctags - Using a tags file to navigate code

See also

• Moodle Security Centre
• Moodle Partners - providers of custom Moodle development services