summer of code

Much of last week was spent reading the new jQuery book that I have just purchased. I have also been playing with the AJAX calls and trying to get the UI to place nice with jQuery and display the forms properly. I started working on a project dashboard too, which is basically and administrator interface to show all projects and their completion across a site. Also I spent time learning how to use joins in MySQL because some of the stuff I am using is getting into more advanced queries and my knowledge of mysql has been limited to just using basic selects to pull out data.

Er, right, this update post has taken longer than it should have. I've been active on the code though, and this time I even have a screenshot for you. Without further ado, I present Commit Log:

Last week was spent still working on UI enhancements and trying to tackle the problem how how to get AJAX to gracefully work if javascript isn't enabled. Later in the week I ended up attending barcamp. At barcamp I met the authors of the first jQuery book, they also gave a presentation on jQuery and answered some questions I had about it for me. I also found out that one of the authors is really involved with the Drupal community, Jon Chaffer. He is known as JonBob in the drupal community.

I'd totally fallen off of writing these updates so I'll start by discussing what I've been up to.

I've got a framework in place for computing, ranking and displaying the metrics. You can view the code that's in my sandbox. I've been able to test it out on a sanitized version of the Drupal.org database.

So files are progressing very well. Work with file_create_url and file_create_path is mostly done but there is still some testing left to do. This is one major portion of getting private/public files working as these functions are responsible for creating the download URLs and paths for files. As always you can check out the code using bazaar from http://drupal.codeincarnate.com. In the near future I'll be looking for testers so if anyone is interested drop me a message or holler at me on IRC if you're interested.

Alright, I have been plugging away at various task. I didn't update last week, but have been making good progress. Much I spent a lot of time with design stuff, learning hooks, API, etc. But have finally started commiting code, after much fuss of learning CVS.

So this has been a good week for files. File uploads are mostly completely working and interfaces are being changed over to use the new file object interface. Right now there is an expected release date of August 5th and most of the code should be done by then. As usual you can check out the current code at http://drupal.codeincarnate.com with bazaar.

Well, I promised you an update on the API module, so that's what you'll get. Just a short notice beforehand: the CVS backend's database structure is now online and available for everyone's reviewing pleasure. Module functions will be added in a week or two, but before that, I'll get the xcvs-* scripts to fill in the entries for the new database structure. I've also made a (slightly different, but largely similar) SVN version of the .install file, you can find that one attached to this post. (As a Subversion backend module is only an optional deliverable, I'd rather not start a versioncontrol_svn project and its directory in CVS just yet.) So it seems to me that deliverable number three, a finished database schema for the CVS backend, can be marked as done.

Get to the point, dude!

Ok, ok. My remaining problem with the Version Control API was that it lacked a way to consistently deal with tags and branches, and to uniquely identify files and directories even if they are not versioned themselves (which is the case for directories in CVS and other version control systems). So I thought a bit more about how to deal with this, and the outcome is a new building block object for items, in addition to the previously existing ones for repositories and commits.

Actually, I wanted to write a piece on how the Version Control API is maturing, but I've got to leave here in a few minutes and won't have internet available until tomorrow, so this must wait for now. Instead, a short coverage of the Version Control / Project Node Integration module (versioncontrol_project.module).

[disclaimer] I'm writing this update while drupal.org (including g.d.o) is attacked by database-eating gremlins, so I can't currently check back on previous entries. Apologies in advance if I mention something that has already been said before. Yes, I could use the Google cache, but that's kinda tedious. [end of disclaimer]

So, I've been pretty absent for quite some time. After getting my university stuff finished, I found a bit less time for my Summer of Code project than I had expected, moving out from the dorms, packing bags, wrapping up undone stuff, whatever. Last week (June 29th to July 7th) I've been attending aKademy, the KDE conference, as previously announced. Great event, great people, great location (this year it took place in Glasgow, Scotland). You can read lots of coverage on KDE Dot News - start here (you can find me in the group photo) and go left in the navigation at the buttom, the marketing team has been active as never before. I wonder in which ways DrupalCon will be different from aKademy, as in my view the projects and their attitudes already differ fundamentally. Ok, so that's that.

Not having found the time before, I reallocated a few hours from aKademy's hacking sessions to my Summer of Code project. Since the last real update, the RCS API module has changed its name to Version Control API (versioncontrol.module), and the former project_rcs.module is now Version Control / Project Node Integration (versioncontrol_project.module). Both now contain a good amount of API functions for accessing commit data. Even if the implementation is still missing out (which, according to the project proposal, has been planned this way), they are the core of what other modules will use from the API module. (Read more...)