Difference between revisions of "Developer documentation"

Jump to: navigation, search
(Guidelines)
(redirect)
 
(47 intermediate revisions by 19 users not shown)
Line 1: Line 1:
[[image:moodle-development-logo.jpg|right|400px]]
+
#redirect [[Main Page]]
 
 
This [[:Category:Developer|Developer]] section of Moodle Docs is aimed at developers who contribute to the Moodle code, plugins, themes, and so on.
 
 
 
* If you manage a Moodle site, [[Administrator documentation]] may suit your needs better.
 
* If you teach using Moodle, try [[Teacher documentation]].
 
<br />
 
<p class="note">'''Note:''' New developer documentation pages should be added to the ''Development namespace'' by typing <code>Development:</code> before the new page name i.e. <code><nowiki>[[New page name]]</nowiki></code>. If you are a developer, you probably want to change your [[Special:Preferences|preferences]] to include the Development namespace in searches.<br /><br />
 
 
 
A page may be added to the Developer category by adding the template <code><nowiki>{{CategoryDeveloper}}</nowiki></code> to the bottom of the page. - If required, you can use <code><nowiki>[[Category:Sort key]]</nowiki></code> to provide a sort key other than the default page name.</p>
 
 
 
==How Moodle development works==
 
 
 
The [[Overview|overview of the Moodle development process]] explains how Moodle development occurs and how people become Moodle developers. Current plans are listed on the [[Roadmap]].
 
 
 
You can also enrol in one of the [http://dev.moodle.org Moodle Developer Courses].
 
 
 
==Guidelines==
 
 
 
The following guidelines are crucial reading for anyone wanting to contribute to the Moodle code base:
 
*[[Coding|Coding guidelines]] have to be followed by all Moodle developers
 
*[[Moodle architecture]] gives an overview of how the Moodle code works
 
*[[Process]] explains how changes are incorporated into Moodle
 
*[[Tracker]] explains the Moodle Tracker for keeping track of bugs, issues, feature requests etc
 
*[[Working with the Community|Working with the Community]] explains how to engage with the dev community and discuss changes
 
*[[Unit tests|Unit tests]] explains how to run the unit tests, and how to write new test cases.
 
*[[Profiling PHP|Profiling PHP]] how to analyse your code to find out why it is slow.
 
*[[Fast portable SQL]] shows SQL techniques that are fast, efficient, and known to work on all supported DBs.
 
*[[Development hints and tips]] a (developing) list of general wisdom to help with your Moodle projects.
 
 
 
==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|developer notes]] or on the [[Roadmap|roadmap]].
 
 
 
The documents below give a general overview. For detailed function-by-function documentation, see the [http://phpdocs.moodle.org/ 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, and you can [http://xref.moodle.org/nav.html?index.html browse the code online] using [[PHPXref|PHPXref]].
 
 
 
===Core components ===
 
 
 
*[[XMLDB_Documentation|Database abstraction layer]] @ v[[1.7]]
 
*[[Roles|Roles and Capabilities system]] @ v[[1.7]] for controlling who can do what
 
*[[lib/formslib.php|Forms library]] @ v[[1.8]] for creating accessible and secure HTML forms that let users edit things
 
*[[Using_the_file_API|File API]] @ v[[2.0]] for managing files stored by Moodle
 
*[[Database schema introduction|The database schema]]
 
*[[What happens when you require config.php|What happens when you require config.php]]
 
*[[lib/moodlelib.php|lib/moodlelib.php]]
 
*[[lib/weblib.php|lib/weblib.php]] for outputting stuff
 
 
 
===Core libraries with a more specific uses===
 
 
 
*[[Authentication API]]
 
*[[Cookieless Sessions]]
 
*[[Email processing]]
 
*[[Environment checking|Environment checking]] before install, check the user's server to ensure Moodle will work there.
 
*[[Groups|Groups system]]
 
*[[Grades|Gradebook]]
 
*[[Moodle Network|Moodle Network]]
 
*[[Question engine]]
 
*[[Stats package]]
 
*[[UTF-8 migration|Migration to UTF-8]] @ v[[:Category:Moodle 1.6|1.6]]
 
*[http://developer.yahoo.com/yui YUI JavaScript library] - YUI was selected as the official AJAX library for Moodle.
 
*[[lib/graphlib|lib/graphlib]]
 
*[[Admin settings|Admin settings]]
 
 
 
===Modules included in the standard distribution===
 
 
 
*[[Lesson Specification|Lesson Specification]]
 
*[[Quiz developer docs|Quiz module]]
 
*[[SCORM schema|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:
 
*[[Modules|Activity modules]], see also [[NEWMODULE Documentation]] (work in progress)
 
*[[Admin reports|Admin reports]]
 
*[[Assignment types|Assignment types]]
 
*[[Authentication plugins|Authentication plugins]]
 
*[[Blocks|Blocks]]
 
*Content editors (2.0 onwards)
 
*[[Course formats]]
 
*[[Course Report Plugins|Course reports]]
 
*Course importers (2.0 onwards)
 
*[[Database fields|Database fields]]
 
*[[Database presets|Database presets]]
 
*[[Enrolment plugins|Enrolment plugins]]
 
*[[Filters|Filters]]
 
*[[Gradebook_Report_Tutorial|Gradebook report]]
 
*[[Gradebook export|Gradebook export]]
 
*[[Gradebook import|Gradebook import]]
 
*Message senders (2.0 onwards)
 
*Mnet services
 
*Plagiarism detection plugins (2.0 onwards)
 
*[[Writing_a_Portfolio_Plugin|Portfolio plugins]] (2.0 onwards)
 
*[[Question_type_plugin_how_to|Question types]]
 
*[[Question import/export formats|Question import/export formats]]
 
*[[How to write a quiz report plugin|Quiz reports]]
 
*[[Repository plugins|Repository plugins]] (2.0 onwards)
 
*[[Resource types|Resource types]]
 
*[[Search engine adapters|Search engine adapters]]
 
*Themes which are different in [[Themes_2.0|Moodle 2.0]], and [[Theme_basics|earlier versions]].
 
*User profile fields
 
*[[Web services (2.0 onwards)|Web services (2.0 onwards)]]
 
*Workshop allocators (2.0 onwards)
 
*Workshop forms (2.0 onwards)
 
*Workshop evaluators (2.0 onwards)
 
 
 
General information that applies to all types of plugins
 
*[[Places to search for lang strings|Where to put language strings for your plugin]]
 
*[[Installing and upgrading plugin database tables|Defining the database tables for your plugin]]
 
 
 
Please see the [[Guidelines for contributed code|Guidelines for contributed code]] for an overview of how to contribute to the Moodle code.
 
 
 
Sometimes it is not possible to write a proper plugin for what you want to do, in which case you may have to resort to using the [[Local_customisation|local customisations]] hook.
 
 
 
===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|tracker]], and attach your change as a [[How_to_create_a_patch|patch]]. It is also a good idea to discuss your ideas in the forums first.  See [[Overview#Major_Development]] for more details.
 
 
 
===Ways to contribute that do not involve PHP programming===
 
 
 
*[[Themes|Create Moodle themes]]
 
*[[Translation|Translate Moodle into other languages]]
 
*[[MoodleDocs:Guidelines for contributors|Help document Moodle]]
 
*[[Tests|Join the testing effort]], which involves [[Tracker|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 [http://moodle.org/course/view.php?id=5 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|roadmap]] or in the form of [[Developer notes|developer notes]]. These pages then form the basis for further discussion in the forums.
 
 
 
*[[Roadmap]]
 
*[[Developer notes|Developer notes]]
 
*[[Student projects]]
 
*[[Developer meetings]]
 
 
 
== Resources ==
 
 
 
*[[Developer FAQ]] - frequently asked questions, especially useful for newcomers to Moodle
 
*[[Finding_your_way_into_the_Moodle_code|Finding your way into the Moodle code]] - also aimed at newcomers
 
*[http://tracker.moodle.org/ 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
 
**[[Firefox tracker search#Firefox Search Plugins|Firefox Search Plugins]] - Find tracked issues even more easily
 
*[[Unmerged files]] - changes on the stable branch in CVS that have not been merged to [[HEAD]]
 
*Browse the code online:
 
**[http://cvs.moodle.org/moodle/ the code with a complete change history from CVS]
 
**[http://xref.moodle.org/index.html the code, with links generated by PHPXref]
 
*[http://phpdocs.moodle.org/ Moodle PHP doc reference] - compiled nightly from the comment attached to each class and function in the code. 
 
*[[Database Schema|Database Schema]] - for recent releases
 
*[http://moodle.org/course/view.php?id=5#4 Development news and discussion] section of Using Moodle course
 
**especially the [http://moodle.org/mod/forum/view.php?id=55 General developer forum]
 
**[[Filters used on the Moodle.org forums|cool tricks you can use in the moodle.org forums]]
 
 
 
== Tools ==
 
Some tools people use when working on Moodle code:
 
 
 
=== IDEs ===
 
 
 
* [[Setting_up_Netbeans|Setting up NetBeans for Moodle development]] - NetBeans for PHP is a great out-of-the-box editor.
 
* [[Setting_up_Eclipse|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.
 
* [[vim|Setting up Vim for Moodle development]]
 
* [http://www.aptana.com/ Aptana Studio 2]
 
 
 
=== Browser add-ons ===
 
*[http://getfirebug.com Firebug], see [[Firebug]] for details.
 
* [[Web developer extension]]
 
* [https://addons.mozilla.org/en-US/firefox/addon/394 ViewSourceWith] - The main goal is to view page source with external applications, but you can do a lot of other things as well.
 
 
 
=== Miscellaneous ===
 
*[[ctags|Ctags]] - Using a tags file to navigate code
 
*[[W3C_validation|W3C HTML validator]] - Moodle has built in support to make using it easier.
 
*[[Windows Installer|Windows Installer]] - Windows Installer documentation for developer.
 
 
 
See also: [http://dev.moodle.org/mod/forum/view.php?id=18 Useful Development Tools forum]in the [http://dev.moodle.org/course/view.php?id=2 Introduction to Moodle Programming course]
 
 
 
==See also==
 
 
 
*[http://moodle.org/security/ Moodle Security Announcements]
 
*[http://moodle.com/partners/ Moodle Partners] - providers of custom Moodle development services
 
 
 
 
 
[[Category:Developer tools]]
 
 
 
[[ru:Development:Краткий обзор]]
 

Latest revision as of 07:04, 7 July 2014

Redirect to: