|
How's this going, Maximino? We have about 5 weeks left to get SCORM 2004 done.
We have fixed a problem with the update of cmi.entry adding conditions in the first php block of the file scorm_13.js.php
We have fixed a problem with the double indexed elements in the GetValue method
We have already fixed some problems with the double indexed elements, but there are still some left. We have been doing tests in order to find the reason why it is not working. It seems like one of the main problems is the maxmodel variable, so we are trying to adapt it to double indexed elements because, right now, the SetValue function is not working when we want to use it correctly for one of those elements.
Assigning to Sadiel for prioritising and fixing.
Assigning to Jesús Rincón to organise and start working on.
We must review some things added from Sadiel like this one.
if (element== 'cmi.interactions.0.learner_response' && value=='Dependency on cmi.interaction.n.type not established'){ errorCode="408"; } In this way we could pass ADL test suite but it's just a test workaround. We have deleted that code and commit the changes to the CVS.
We have been searching the code to find some errors and we realized there were a problem with the CMIFeedback and with the double indexed elements and we communicated it to Bobo, who has already solved some of those bugs. We continue working on this.
Fixed a bug with cmi.interactions.n.id elements. Now it sets the value correctly instead of showing the error 351, as it used to do for some tests.
We fixed a problem with duplicated ids for cmi.interactions.n.objectives.n.id elements.
We fixed a problem with duplicated ids for cmi.interactions.n.id elements.
We and Bobo continue working on the CMI Feedback type definition. We are solving different bugs related to the dependency we have to establish between this type and the cmi.interactions.n.type.
Fixed a problem with the type "sequencing" for CMIFeedback.
CMIFeedback is done for learner_response. We are working on the correct_responses type.
Working on the definition of the correct_responses type
Working on some javascript errors on the definition of correct_responses.
Fixed some errors of duplicated elements and with the number of patterns.
Fixed a problem with true-false type for correct responses.
closing this as a duplicate - will use the parent of this bug for tracking details regarding to SCORM 2004 compliance.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
There still remains some problems and we need to introduce sequencing to complete all the things.
Please update every day your version.
Bobo.