Donate to Wikipedia

Thanks

Finally Made a final last push to my gsoc project today and Submited all code for integration to Moodle Core.It was really an awsome experience working with the whole Moodle community.Really thankful to such awesome people in the community.Dan Marsden and Helen Foster were really supportive and helping through the project. Dan , I learnt a lot of things from you and hope to learn even more in future.

All in all it was one of the best experience of my life, and hope moodle community also benefits from the codes I have submitted.

Reference -

Github Moodle Fork

Moodle Tracker

Commits already integrated in Moodle

Past few weeks I spent on building the Interractions plugin for Scorm reporting(Reference- MDL-28277)

The work is almost complete now..and as soon as its finally cleaned up a bit..it can be integrated to the moodle core.

I am glad to all let you know that my first subtask (Reference-  Post, MDL 27522) is now a part of Moodle core (Reference-  Git Commit) after going through rigorous  review and testing.

Past couple of weeks I have been working on the second sub-task of my project “Creation of plugin container and basic reporting plugin” (Reference- MDL 27523 ). The initial module design used a database table. But later on the plugin structure went through many updates based on various discussions with Dan, and was finally decided to go with a table less structure. The work of the plugin is completed and ready to be integrated in the core (Ref- Git Tree). Now its time for the codes to go through integration review and testing.

In the meanwhile I have moved on the work to the next subtask “Design of a interaction report plugin”(Reference- MDL-28277).

Past couple of weeks I am working on one of the major sub-task of my Gsoc Moodle project – Separate generation of user report from main SCORM reporting (Reference – MDL 27522 , MDL 27256 ). I have completed the work on this subtask. Dan has also reviewed and approved the codes. Now we are waiting for peer review, so that the code can be pulled up in the Moodle core.

Here are links to the codes and the diff :-

Tree

Diff

Hopefully the it will be pulled up in core soon, Untill it is pulled am moved on my work to next major subtask “Creation of plugin container and basic reporting plugin” (Reference MDL 27523 ) .

• Login to dashboard
• Click on any revisions of any of your post.
• Select the same revision in both radio columns and Click compare.
• See the Magic!!

You will get something like this:-

So scare your friends before they become aware of this.

This is a post in my Gsoc Project Series.

I am glad to let you all know that I have moved from basic planning to some execution already. We have categorised some basic milestone that we need to achieve. One of the first prerequisite for building the plugin container was breaking down the features and moving common features outside report.php, so all custom plugins will be able to use it.Detailing user attempt details and its trackdata is a generic feature which most plugins might need to use, hence we divided to move it reportuser.php.

So this week I spent separating the two files and generating new file reportuser.php(besides planning the plugin container and other stuff).

Now I need to validate the code structure a bit and remove any unwanted pieces of code and do some other optimization before it can be pulled into the Moodle core. https://github.com/timhunt/moodle-local_codechecker

seems like a good way to validate code for moodle, I used it earlier only once, but it was a really nice and promising plugin .

Untill next update, signing off

Ankit

This is a post in my Gsoc Project Series.

During the past  Week I have been working on a lot of stuff for the GSOC project.A lot has been accomplished. Basically the idea and structure of the module to be designed is lot clearer now. The basic design will consists of :-

• core plugin container.
• A basic reporting plugin.
• A advanced reporting plugin.

The core plugin container will act as the heart of the module providing a base and platform on which custom plugins can be built.

Its also proposed to include atleast two plugins be default with the container in the Moodle core. The first one will handle normal reporting modes as the current plugin does and the other one will handle basically advanced reporting. Structure and exact features of this plugin is yet to be discussed and finalized.

Updated specs can be found HERE.

The main objective, in general, of the project is to improve SCORM reporting for Moodle. The present Moodle SCORM reporting doesn’t handle and interprets SCOs properly. This project aims at converting the current report to a pluggable architecture, So that custom reports as plugins can easily be incorporated with the SCORM module.

The detailed specification is in the process of regular refinement based on user feedback. Updated specs can be found HERE.