Some small edits to the wrapper: Fixed a few typos in debug statements Added extra error-checking during SCORM.connection.initialize; if connection cannot be made AND no error code is given, display notice that server has not responded. Related links: Original SCORM API Wrapper journal entry pipwerks.com SCORM page
Most e-learning tools do not promote the creation of effective courses, web standards, or accessibility; they merely make cookie-cutter course development easier for technically inexperienced course developers.
I’ve been a longtime user of the ADL wrapper (with code from the late Claude Ostyn), and to be honest, it’s pretty much met my needs. But I was never completely comfortable with the wrapper for two reasons: 1) The code is hard to read with confusing and overly complicated looking variable names, and 2) the code made heavy use of global variables, which in this Web 2.0 world is a big no-no. This past week I decided to roll up my sleeves and make a new SCORM API wrapper that takes care of these issues.
Folks, it’s simple — if you have to paste a “this site works best with XXX browser” message on your site, whether it’s an LMS, an online course, or just a website for your mom’s knitting club, you’re doing something wrong. Do us a favor and stop it.
These are video profiles of people with disabilities — mild to severe — who use assistive computer technology to improve their lives. Some people use the computers to simply help them with their jobs (such as a blind person who is a professional French-to-English translator), while others use their computers as a lifeline to the rest of the world.
Armed with a basic understanding of accessibility, and with a little planning, a web developer can create courses and/or websites that contain rich content — even Flash movies and videos — while supporting a majority of assistive computer/alternative web browsing technologies.
Everyone knows the story: an innocent email address is posted online and a big bad spambot finds it, relaying it to every spammer on the face of the earth… the email address becomes useless due to the 500 spam emails you get every day!
Every now and then, a developer will come up against something that was SOOOO easy with table-based layouts and winds up being a royal pain with CSS-based layouts. One of these “d’oh!” moments is when you try to vertically center an element on your web page. Umm… hang on, let me rephrase that: One of these “d’oh!” moments is when you try to vertically center an element on your web page when using Internet Explorer 6.
This week I needed to create an XML Schema doc for work. The XSD file would be used to validate XML files I’ll be making for my online courses. Well, being a newbie to XSD files (though not XML), I was making decent but very slow progress when a thought occurred to me: it should be possible to reverse-engineer an XML file to create an XSD file.