Cool, my initial work has been checked into cvs and is now available from HEAD. This release adds indexing and searching of wiki pages to Moodle. I don't really have much else to say, hopefully it doesn't crash and burn when someone other than me tests it!

After mucking around with XDebug for a while (APD's pprofp seems to not like very large log files, as it just quits silently after thinking for a while), and discovering that XDebug 2-beta isn't exactly what I want (have to install KCacheGrind and stuff to view the logs, and I don't want to install any KDE libs), I decided that my stopwatch(); function would have to do for the time being.

Anyway, so indexing 5734 wiki entries varies between 140 - 180 seconds, I got 157.405181 seconds on my last run, and takes up close to 3MB of space on disk. Querying this index takes about half a second, as you can see in the attached file.

Wahoo !
Today was a really sprint coding, I didn't stop for long and I've now finished my first prototype.

So, what have we got ?

• a base GUI (but fully functioning)
• all JSDoc commented classes
• a base XML structure
• a VERY BASIC download and launch application (unchanged from my "test-app")

Now that I've tested on separate "test-apps" all the functions I would like to implement in my first working prototype I think I'll now begin to code a very early prototype.

The first thing to do will be to organize my files and to create the branch on the CVS repository.

Then I'll have to begin making a "distributable" code.

So, as announced, let's try to find what the different features are and which are skippable until the end of the development time, which ones are very necessary, and so on...

So there are my ideas, from the most important (what as to be implemented on the first prototype to the more optional)