The pipwerks SCORM Wrapper has been updated with a small patch for handling odd behavior in the Plateau LMS. Special thanks to Joe Venditti for the patch (and sorry for taking almost 2 years to add it to the codebase!).
Get the latest version here.
Comments
Bobby wrote on August 10, 2011 at 7:31 am:
Thanks for the update Philip! I test my content outside of a LMS environment. In that case, the code you've introduce causes a javascript error since win.top.opener is null. To combat this, I check for win.top.opener before checking for win.top.opener.document.
I'm not sure this is worth adding, as I realize I'm in a unique situation. Just thought I would share my findings. Thanks again!
philip wrote on August 10, 2011 at 8:05 am:
interesting. thanks for the info.
tami wrote on August 25, 2011 at 7:20 am:
what if i have more functions in my original APIwrapper? (which i used with as2)
can i simply paste them to this one?
philip wrote on August 25, 2011 at 7:43 am:
you're free to modify the wrapper as needed. if your custom functions were written for my previous pipwerks wrappers, you can probably copy and paste. if they were for non-pipwerks API wrappers, no, you can't just copy and paste. regardless, any modification should only be done if you have a good understanding of the wrapper and understand the effect your modifications will have.
Thanks for the update Philip! I test my content outside of a LMS environment. In that case, the code you’ve introduce causes a javascript error since win.top.opener is null. To combat this, I check for win.top.opener before checking for win.top.opener.document.
I’m not sure this is worth adding, as I realize I’m in a unique situation. Just thought I would share my findings. Thanks again!
interesting. thanks for the info.
what if i have more functions in my original APIwrapper? (which i used with as2)
can i simply paste them to this one?
you’re free to modify the wrapper as needed. if your custom functions were written for my previous pipwerks wrappers, you can probably copy and paste. if they were for non-pipwerks API wrappers, no, you can’t just copy and paste. regardless, any modification should only be done if you have a good understanding of the wrapper and understand the effect your modifications will have.