Note: You are currently viewing documentation for Moodle 2.0. Up-to-date documentation for the latest stable version is available here: Student projects/Messaging improvements.

Student projects/Messaging improvements: Difference between revisions

From MoodleDocs
No edit summary
(Shifted to dev docs)
 
(21 intermediate revisions by 5 users not shown)
Line 1: Line 1:
'''Programmer:''' Luis Filipe Romão Rodrigues
{{Moved_to_dev_docs}}
 
=Summary=
The Moodle messaging system in Moodle is a bit clunky and could use improvements to make it slicker and more efficient as a tool for messaging people within the Moodle environment.
 
Functionality improvements:
* Add a messaging API class to the core of Moodle which all modules will start using for sending messages (currently they all format their own emails).
* Add output plugins to messaging so that users can choose exactly how to route their messages, especially when they aren't online at the time.  Initially the two plugins would be "browser" and "email", but later there could be a jabber plugin, an IRC plugin etc)
 
Gui improvements:
* Improve the main message GUI using AJAX (Moodle includes the YUI library so you'd need to use that)
* Improve the messaging window to allow chats among three or more other people at once.
* GUI for the output plugins to allow users to set rules about each plugin independently, and also to select from incoming messages by type, by user or by moodle module.
* Improve the methods to search messages and find discussions from the past.
* Improve administrator auditing of message logs, including filtering etc.
 
=Project Information=
 
==User Profile mockup==
[[Image:Lfrodrigues-_messaging_config.jpg]]
 
==System Overview==
[[Image:Lfrodrigues-_messaging_config.jpg]]
 
==Possible implementarions==
I see two ways of implementing this. My main problem at this stage is that I really don't know if there are real peformance gains with a new system.
===Using Events===
New messages are posted as events. The core messaging code has a handler to grab them and to choose how
to process them.
 
Martin told me that if the system gets too "popular these messages become COULD be a little heavy on the system".
 
This approach seams the easiest a better because I would reuse a lot of code (good software practice) but don't know about the performance escalates 
===Develop a new class===
I could also implement a completely separate and probably much simpler system where all modules just call a function to add a new message to a queue. The system would the process the messages and choose how to process them.
 
==Changes==
===Files that need changing===
 
With modules/files need to be adapted to the new system?
* the ones with send email
* ??
 
===Modules/Files with send emails===
 
This modules/files send email using email_to_user, is there any other?
 
Modules:
 
* journal,
* forum,
* lesson,
* workshop,
* assignment
 
Other files that need changing:
* /lib/moodlelib.php
* /admin/process_email.php
* /enrol/imsenterprise/enrol.php
* /enrol/manual/enrol.php
* /enrol/paypal/ipn.php
* /enrol/flatfile/enrol.php
* /enrol/authorize/uploadcsv.php
* /enrol/authorize/localfuncs.php
* /error/index.php
* /message/lib.php
* /backup/backup_scheduled.php
* /course/pending.php
 
 
 
 
 
Back: [[Student_projects]]

Latest revision as of 03:51, 15 September 2011

This development related page is now located in the Dev docs.

See the Student projects/Messaging improvements page in the Dev docs.