SoC

The first release of DAST is available on d.o: http://drupal.org/project/DAST. See the INSTALL.txt and README.txt - you'll need to download additional dependencies from http://www.abeharry.info/stuff/dast-deps.tar.gz or http://www.abeharry.info/stuff/dast-deps.zip A guide to using the dast-patch build file is available here: http://groups.drupal.org/node/5124 I'd appreciate feedback from anybody who wants to try it out - for what the project is trying to accomplish see here: http://groups.drupal.org/node/3913 .

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.

This week I got some feedback for the first parts of the taxonomy manager. People provided me with additional ideas, that's always great. Again I thought about some points, like how to manage term weights or how to do merging.

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).

This week I'm making the first release of the XMPP Drupal module. It basically wraps the functionality of the latest library version, giving you an interface to configure the client and send test messages. I would love to get some feedback both on the user interface and the actual functionality, since so far I've heard very little regarding the two library releases. You can grab the module archive from my site, be sure to read what I posted regarding the configuration steps.

-Max

[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...)

So this week saw the successful completion of file uploads! When files are uploaded a private flag is successfully set in the database indicating whether the file should be private or public. There is more work to do to transfer some functions over to the new file object interface and also an administrative interface will probably be made. As per the usual you can check out the latest code with bazaar from http://drupal.codeincarnate.com.

After finishing my exams last week, I finally had much more time to work on my project this week as the last time.

So I started with coding. The first task was to write a simple jQuery script for a dynamic tree view (collapsible parents) for a vocabulary.

Last week was spent giving much overview of the code, as well as starting to play around with the layout and design of the forms. I spent a lot of time catching up on some of the drupal dojos. Diving into the nodeAPI as well as forms API. and spending much time on api.drupal.org to figure out what the current functions in the current case tracker module are doing. I spent some time learning some of the jQuery syntax as well as AJAX ( I am new to programming w/ AJAX). I also spent time learning CVS for drupal.