In my last blog, the screenshot showed a broken image.

Thanks to some very fast work by Tobias König (tokoe), it now works. That picture of Konqi was uploaded to the server using Outlook, and downloaded using OpenChange and Akonadi, before being rendered.

(again, click to expand).

Thanks again to tokoe.

Spent some time today getting the OpenChange resource for Akonadi up and running again. I haven't really done anything to improve it from where it was a few months ago (OK, September 2007, when I was on holidays), but it lives again.

Those few months have involved a lot of changes on both the OpenChange side and on the Akonadi side of this resource. However we can still read mail (kind-of) and show contacts (kind-of).

Screenshots, using the akonadiconsole tool:
,
(click to see full size).

Haven't blogged for a while, mainly because I didn't have much worth saying. I still don't have a lot worth saying, but I'll blog anyway.

I recently became part of the OpenChange team. For those not familiar with it, the OpenChange project is developing a client and server implementation of the "MAPI" protocol (which is really Exchange RPC - MAPI is the API you use to access the transport) used by Microsoft Outlook and Microsoft Exchange. OpenChange is the key to implementing an Akonadi resource that can work with Microsoft Exchange.

Thiago has set up the KDE Summer of Code 2008 ideas page. Thanks!

For those that missed it, Microsoft recently released some of the specs relating to their office suite (http://www.microsoft.com/interop/docs/OfficeBinaryFormats.mspx).

Naturally, they probably aren't everything we'd like to have (various people have suggested that they aren't complete, and I'd be surprised if there wasn't something omitted, more likely because of incomplete records than because of deliberate omission - the PR downside to deliberate omission becoming public would be a disaster).

For those that missed Aaron's Plasma tutorial at linux.conf.au 2008, the good news is you can now view it online.

Recent development has left me feeling a bit unhappy with part of my toolset - code coverage. I'm not especially interested in metrics (except as a guide to where to start) - rather in the detail.

gcov does part of the problem, but it really only works at the level of "lines executed", and doesn't do much for shared libraries.

I finally got the KCabinet class (in playground/libs/kcabinet) working.

I've just checked in the start of a new class - KCabinet. Its in playground/libs/kcabinet for the morbidly curious. I'm not sure if it is really going to be right for kdelibs - need to get it a bit more mature before needing to make that decision.

The format is reasonably well documented, at http://msdn2.microsoft.com/en-us/library/bb417343.aspx, and there are other tools that can read it.

You may (or may not) know that Okular can read the Oasis Open Document format (aka OpenOffice.org text format or OpenDocument). It doesn't render the document exactly as oowriter would, but it is quite a bit faster to start up I tried to open an encrypted document with it though, and it failed. A couple of evenings later, and I have a patch that "fixes" Okular.