Development:Messaging 2.0: Difference between revisions
From MoodleDocs
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
<p class="note">'''Note''': This page outlines ideas for further messaging improvements. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Messaging 2.0|page comments]].''</p> | <p class="note">'''Note''': This page outlines ideas for further messaging improvements. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Messaging 2.0|page comments]].''</p> | ||
==1. Revise 2007 code== | |||
First steps are to review the current code: | |||
# [http://cvs.moodle.org/contrib/patches/messaging_v2/ 2007 code]] | |||
# Make code conform to [[Coding| Code guidelines]] | |||
# Add phpdocs | |||
# lib/messagelib.php | |||
# Review from mentor and other programmers | |||
# Check into HEAD | |||
# Continue polishing as necessary | |||
==2. Extend basic messaging system== | |||
# Store content formats for each message and use these when routing messages. eg HTML messages from forums should be converted into basic text, etc Sometimes certain message types won't be possible to route to certain output plugins - the GUI should indicate this clearly. | |||
# Test everything very well. | |||
==3. Enhance the messaging popup GUI== | |||
# Examine the requests in the tracker, edit/prioritise/improve them | |||
# Publicise the project in the forums, ask community to file issues and/or vote on them | |||
# Tackle the most wanted items first | |||
Revision as of 06:06, 26 May 2008
Note: This page outlines ideas for further messaging improvements. It's a specification under construction! If you have any comments or suggestions, please add them to the page comments.
1. Revise 2007 code
First steps are to review the current code:
- 2007 code]
- Make code conform to Code guidelines
- Add phpdocs
- lib/messagelib.php
- Review from mentor and other programmers
- Check into HEAD
- Continue polishing as necessary
2. Extend basic messaging system
- Store content formats for each message and use these when routing messages. eg HTML messages from forums should be converted into basic text, etc Sometimes certain message types won't be possible to route to certain output plugins - the GUI should indicate this clearly.
- Test everything very well.
3. Enhance the messaging popup GUI
- Examine the requests in the tracker, edit/prioritise/improve them
- Publicise the project in the forums, ask community to file issues and/or vote on them
- Tackle the most wanted items first
See also
- GSOC/2008
- Messaging improvements, a GSOC 2007 project
- MDL-10107