Development

It's still a bit premature because we'd like to try it out a few times more before officially announcing it on the website, so if you want to help, feel free to download your version from here: http://www.dokeos.com/download/dokeos-1.8.5.zip In a few hours from now we will make the official announcement, so the official release date will be the 12th of June anyway. If you happen to witness some wierd thing in the install or upgrade procedure, please, let me know as soon as possible! Otherwise, just enj

After having a look at a nice little game in Python (Frets on Fire, try it, it's a game of the likes of Guitar Hero, totally GPL) and seeing that they had a "code walkthrough" page on their wiki, I thought that the name "code walkthrough" was very explicit and helpful so... I have put together a few lines of explanation regarding the Dokeos 1.8 code for those who just joined the Dokeos development community. http://www.dokeos.com/wiki/index.php/Dokeos_1.8_Code_walkthrough It's not much but hopefully it might save

I don't know about you, but I really don't like the Dokeos footer moving around the screen when there's less content. Luckily, CSS offer an easy way to change this. Let's say I want to update the css/dokeos_classic/ theme. The rule, as always, is to make a copy of the directory that is the closest to what I want, and only work on a copy, so I'm going to do that.

I'm currently reviewing (together with Thomas and Julio) the latest things to be done before we officially release Dokeos 1.8.5 stable. The list is available in our bugs tracking system and will obviously change a lot before tomorrow.

A few typos went into the upgrade code from 1.8.4 to 1.8.5 RC1, so if you went through this particular setup, you're going to have to fix a few things manually:

1. The queries about the required fields in the user profile were missing a quote, so you want to execute, inside your main database, the 3 first queries below
2. It won't help you much as the error has already been made, but the survey tool that now appears in the interaction section is visible by default, which is acceptable for a new course, given the teacher has to go through it anyway, but is not (acceptable) for an ex

Not that I've been too busy on Dokeos lately (I tend to take my mind off Dokeos for a couple of days after a release), but it's going to come back very fast now as we are warming up for the last run to Dokeos 1.8.5 stable. So, what's on the menu? Well, apparently there are still *some* bugs about the course copy and SCORM export somehow. Thomas filed a bug for me about this.

LETSI, Learning Education Training Systems Interoperability, is entering a phase of study for the next version of SCORM, version 2.0. Of course, given the little level of adoption of SCORM 2004 (or 1.3), this might seem a little premature for some, but the making of such a large norm takes time, so it's probably better to get started early. The 2.0 version is said (in the announcement of the

These days, I'm trying to get a little bit closer to the Drupal community, locally, in Lima, Peru, where I live at the moment. This community seems about the best I can get, close to a PHP-developers community. So the next event I'm organising home will be a reunion for Drupal developers, on the 28th of June, in Miraflores, and then I'll probably have it monthly or something like that.

I've updated the Dokeos 1.8.5 page to reflect the fact that we now have a Release Candidate and are very close to the stable release. This is a time for us (developers) to take a deep breath and analyse things with the satisfaction of someone having done a nice job.

We officially released 1.8.5 RC1 tonight, although we might alter the package just for two little microscopic changes tomorrow morning (one concerning SCORM export on Dokeos installs that use a subdirectory of the web server document root, and the other implementing a default hiding of the audiorecorder for the learning path building tool). I think there's not much to say, other than it's a *great* unstable release. I find it amazing how much we can progress with a good team.