Note: You are currently viewing documentation for Moodle 2.3. Up-to-date documentation for the latest stable version is available here: Roadmap.

Roadmap: Difference between revisions

From MoodleDocs
Line 15: Line 15:
:: These three are separate but complementary so will be developed together.
:: These three are separate but complementary so will be developed together.


* [[Development:Conditional activities|Conditional activities]] - Moodle.com
* [[Development:Conditional activities|Conditional activities]] - Open University (Sam Marshall)
::Allowing dependencies and forced paths through activities: ie "You can't do this thing until that thing is completed".
::Allowing dependencies and forced paths through activities: ie "You can't do this thing until that thing is completed".



Revision as of 07:27, 18 June 2008

This roadmap collects the best information about upcoming features in Moodle. It is not 100% certain - features may change according to available funding and developers.


Version 2.0

Expected very early 2009.

Major features

  • Moodle 2.0 will require PHP 5.2 as a minimum, allowing us to clean up the code in some areas. For more info see: gophp5.org.
  • File handling improvements - Moodle.com
    • File API - maintains an internal repository of files and governs access to them
    • Repository API - allows users to browse external repositories and select files to bring into Moodle
    • Portfolio API - allows Moodle content to be captured and pushed out to external repositories.
These three are separate but complementary so will be developed together.
Allowing dependencies and forced paths through activities: ie "You can't do this thing until that thing is completed".
AKA Proper competency tracking, so that individuals can have learning plans listing outcomes/courses which are updated when courses are completed.
Replaces our ageing HTMLarea with a new one that works on more browsers, enforces XHTML strict and better integrates with the new File API
Makes it easy for users to find and navigate other systems and external Moodle repositories, leveraging the Moodle Network in various ways.
Standard set of core API functions made available via SOAP and XML-RPC
  • Old DB install/upgrade system removed - Moodle.com
The deprecated system for installing or upgrading database entries used in Moodle < 1.7 will be completely removed, while supporting only the new XML based database scheme introduced in 1.7.
MDL-14679 Database access is to be refactored so that: we can use prepared statements everywhere for increased security and some performance, we put datalib functions in a class to allow better unit tests (mock db), and remove the need for slashes in userspace. This will cause breakage for 3rd party modules (but fixing them won't be too hard).
refactor Blocks and Pages using contexts to allow blocks to go anywhere in Moodle with better control.
interface that allows teachers to specify exactly when a course should be considered finished for each user
Polished and included as a core module.
  • New Wiki module (nwiki) - DFWikiteam-UPC
To be cleaned up and included as a core module.
Major improvements to the quiz reports, especially regrading and item analysis.
Add commenting to blogs (MDL-8776), as well as support for external blogs
Refactor messaging to use plugins for input and output, controlled by users
Obscure RSS feed URLs using private keys, controlled by users.
  • More tagging
Tagging of courses, activities and other things
  • AJAX for gradebook User Interfaces
A host of UI improvements to enhance usability and speed

Hopefully

API for integrating external systems for managing student information
Moodle Voice is a project for embedding VoiceXML support into Moodle Core.
We plan to have a very simple export for any Moodle course into IMS LD format, as a proof of concept and to help the community start learning about IMS LD.
Usability improvements for new and established users through increased field testing, selective feature availability, and research (such as the GSOC project).

See also