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!

In the time I was reading MDB2_Schema documentation I had noticed that the parameter section of class methods could led to missunderstanding in some cases.
Now that I have learned how to use CVS that would be a good job to start with. Before getting access to CVS I have dumped the HTML (output by PEAR's site) to my local machine and proposed a new style for parameter section here. Having an idea on what should be changed in the HTML and getting those changes approved by Pierre was the first step to take.

For many years I have been haunted by CVS, this time I couldn't avoid it though. I have got my PHP CVS account set so that's time to start playing with it. I had no idea where to begin. My best bet was the web interface for the PHP CVS repository where I could found the link:

http://www.php.net/anoncvs.php

The first step to get in php CVS tree:

cvs -d :pserver:login@cvs.php.net:/repository login

Downloading MDB2_Schema to my local CVS repository:

cvs -d :pserver:login@cvs.php.net:/repository checkout -d MDB2_Schema pear/MDB2_Schema

Well I have done several cvs commits. But the real big one is coming soon! Right now you can see my current code, which works PERFECTLY (or so I assume) with nodes. It is still very basic but it will and can recommend only certain types of nodes (i.e. story, or page, or whatever you want) and it can recommend the best nodes no matter the type.

It also has a function that recommends items that are similar to the current node.

This is how it is set up....

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.