Added code to handle seeked event and trigger an xAPI statement

added code for sending following events
-seek
-volume change
-fullscreen
-play
-pause
-Initiated

I haven’t actually been able to get the fullscreen event to trigger

Used Youtube Video API to implement:
-Seek
-Play
-Pause
-Initiated
This is all that was possible via their API

Play wasn’t firing with play button was hit all the time so I added functionality in the state change event to evaluate if play event needed to be triggered.

Moved completion params into a function

Haven’t been able to get this code to call for testing in any video upload with Wordpress so I am not adding functionality for this.

Fine tuned seek event more.  It is working very well on HTML5 still need some work on Youtube for the events when a user is scrubbing.

Made sure all floats in played segments were formatted to correct precision

maintainer uses 2 spaces for indentation, make sure to follow this style.

Use template getArgsXAPI{verb} instead of getxAPI{verb}Object

xAPI verbs are past tense, so make the function names match.

html5 video object has a property called currentTime, not current_time

Added code to handle seeked event and trigger an xAPI statement

added code for sending following events
-seek
-volume change
-fullscreen
-play
-pause
-Initiated

I haven’t actually been able to get the fullscreen event to trigger

Used Youtube Video API to implement:
-Seek
-Play
-Pause
-Initiated
This is all that was possible via their API

Play wasn’t firing with play button was hit all the time so I added functionality in the state change event to evaluate if play event needed to be triggered.

Moved completion params into a function

Haven’t been able to get this code to call for testing in any video upload with Wordpress so I am not adding functionality for this.

Fine tuned seek event more.  It is working very well on HTML5 still need some work on Youtube for the events when a user is scrubbing.

Made sure all floats in played segments were formatted to correct precision

maintainer uses 2 spaces for indentation, make sure to follow this style.

Use template getArgsXAPI{verb} instead of getxAPI{verb}Object

xAPI verbs are past tense, so make the function names match.

html5 video object has a property called currentTime, not current_time

…-video into add-xapi-video-verbs

Moved all statement creation of xAPI video objects to a separate file x-api.js

This should have been commited with the last commit.  The statement generation was moved out of this file to the x-api.js file.

Changed to match video profile.  Completed statement can be differentiated from H5P interactive video completed statement due to object.id.

Added some items to completed per Jon’s request and ensured decimals in seeked were being fixed to a decimal count.

Add description comments to input variables

parseInt() fails on small numbers.
Video durations less than 32 seconds will use scientific notation when doing the year calculation (e.g., 8 seconds => parseInt(8*(365*24*3600)) == 2.53e-7), and parseInt() will convert this to 2 instead of 0.
See: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/parseInt#Description

@see h5p#17 (comment)

h5p#17 (comment)

See https://developer.mozilla.org/en-US/docs/Web/API/Document/fullscreen

xAPI Video Profile spec was updated to use “completion” instead of “success” in the result object. See:
https://liveaspankaj.gitbooks.io/xapi-video-profile/content/statement_data_model.html#252-completion

also include note about avoiding parseInt() because it cannot handle exponential notation.

In getProgress a current segment is ended.  I removed an uneccessary if statement below this that made a segment from the current time to the current time.  getProgress is also called in html5.js and youtube.js before determining if getArgsXAPICopmleted should be called.  getArgsXAPICompleted was also calling getProgess which results in another segment of current time to current time which is meaningless so I made progress an input to getArgsXAPICompleted so this call is only made once and the segment is ended without a meaningless one being added to the segment string.

…-video into add-xapi-video-verbs

playedSegments was being stored as a string, requiring parsing to array and manipulating whenever progress was queried. Refactor playedSegments to an array, and only stringify it when sending an xAPI statement out.

strings wrapped in single quotes;
add missing semicolons;
strict comparisons;
else starts its own line.
See: https://h5p.org/documentation/for-developers/coding-guidelines