Development

Yesterday I finished a 20 hours job of moving the SCORM API in Dokeos 1.8.6 from XAJAX to jQuery.

It has been my understanding, since a few years back, that setting

php_admin_value error_reporting "E_ALL"

inside my Apache's VirtualHost configuration actually permitted to set the error reporting to all types of error. Recently, upgrading Ubuntu from 8.04 to 8.10 (I don't know exactly which versions of PHP5 that actually meant), several of our team have seen their error reporting disappear... I first thought this was related to XDebug, installed on all our computers, but disabling it didn't fix anything. After 2 hours of searching for pretty much any topic related

I felt upon this website while checking out a few web development extensions for Firefox: http://ipinfo.info/netrenderer/ Basically, the site allows you to check what a website would look like under IE5, IE6, IE7 and IE8 Beta by simply taking a screenshot of the website actually opened in one of these browsers.

Here are some more of my reference sheets (one on plugins/tools development and one on security). dokeos-185-tools-and-plugins-quickref dokeos-185-security-quickref I think with that I cover all basic questions a new developer might have, except the system to install/upgrade a Dokeos install (changing SQL queries) and the way to actually query the database using the Database class.

I've been working for 4 years on the Dokeos code now, and that item_property table bugged me more than once. It's a clunky, unclear table which holds pretty much all the visibility rights of all the resources in a course. It's quite impractical to deal with visibility in itself, mostly because it only allows for a visible/invisible flag (which is insufficient for most finely-grained permissions systems), and because it holds a super long list of other attributes that you always have to set, and that are never used in the end.

Extending a little bit on my latest post about howto test SCORM interactions in Dokeos, I'd like to add an important piece of information about our implementation of the SCORM 1.2 standard (and specifically the interactions). Although the SCORM 1.2 Runtime Environment documentation is not very clear about this, there are two "hints" that interactions IDs must start at 0, and not at 1. First, the description of the SetValue() method on cmi.interactions.n.id says:

De

Following up on my previous post about the differences between the mbstring and iconv international characters libraries (which resulted in a tentative conclusion that nobody knew anything about those differences), and particularly the comments by Nicola, we have combined forces (mostly efforts from Nicola, actually) to provide you with a little benchmarking, if that can help you decide. Nicola wrote the following script (which he gladly releases as public domain license) to test th

Because one of the most complicated tools in Dokeos is the SCORM tool (found in dokeos/main/newscorm/ ), and because I am currently checking the inner-workings of the interactions inside this tool (Dokeos version 1.8.5), I thought it would be good to write down, once and for all, how I actually check whether the tool is right or wrong, and whether the content is actually the culprit or not.

Getting the right tools

The elementary tools for these tests are Firefox (I recommend version 3 for its better handling of JavaScript debuggi

I don't know how to call this post. I have a problem with patch (I'm too bad to get it t work properly) so I want to export a list of the files I have modified between two subversion commits. This is how I do it for now (I'm sure it's extremely perfectible).

svn co http://mysvnproject/trunk/project@1

This gets me the first version

svn update > diff-files.txt

This updates my copy to the latest version, but most importantly, it generates a list of files that have been updated or added.