Today started with the usual thing in the morning, a breakfast. Everyone was pretty cheerful, we did not end that late in the night. I wonder if that has to do with Tobias not being around ;-).

After the usual email checking and writing down whatever has come up during the night, we went on to do the KMime review. Stephen has made kind of a wrapper for KMime, which is the library Mailody uses and KMail should use for dissecting incoming mail messages, splitting out attachments, showing a certain part etc. It is also used for composing messages, which is the relevant part here. A mailcomposer usually has settings like the addressees, attachments, crypto settings, etc. Stephen’s classes easy the work to get this to the actual message that has to be delivered to the smtp-server. It works with ‘Strategies’, so you have a signing strategy an attachment strategy, if you provide a html-text, the plain text has to be added with an alternative strategy, etc. Cool stuff.

We also did a developer-feedback round. Every app developer was given the time to ask questions about Akonadi, to see what are the flaws in the API and what can be improved. Also this afternoon we put on the diff between the 4.1 branch and trunk and reviewed all the changed API. Checked for consts, @since 4.2 marks, consistent naming, etc. Only like 3000 lines of code, so that was over quickly, though we did it thoroughly.

Besided these group things we also worked on our own projects. Curious what everyone did? I asked around and this is what they told me: Will worked on Network Manager for KDE4. A bit that’s badly needed in KDE4. He fixed bugs in the usage of KWallet, thought of creative ideas to use KConfigSkeleton to save code. In the meanwhile he also tested the Akonadi Resource Migration from an end-user perspective. Kevin has been working on distribution list support for Akonadi and respective changes in the migration bridges. Thomas has worked on the migration a bit so that the old kresources are now disabled after migration and the new ones are made the default.

The ‘Migration’ is the goal we are trying to reach. In 4.2 it could be that we will switch on Akonadi for a couple of resources. This involved no changes for the applications as there are bridges, so the application thinks it’s dealing with a traditional resource. Of course that means the addresses has to be migrated flawlessly.

Bertjan added support for remote files to the vcard and ical files resources. Also added the shiny overlay widget to the KPilot Akonadi related configuration dialogs. This overlay will becomes visible when there is a problem with the Akonadi server and clearly states the problem. Widgets can subscribe to this overlay, so it gets this message and the original functionality is disabled. This prevents every single widget checking if Akonadi is available. Volker added that a few weeks back.

Volker finished the kres-migrator integration in kresources and worked on getting a kolab calendar working with both compat bridges and Akonadi. Also he answered a gazillion questions about all aspects of Akonadi.

Stephen presented feedback on Akonadi framework gathered while developing kjots plugin. Presentation and design review on new KMime classes which make constructing complex mime messages easier. Review and commit of several Akonadi patches including mixed model for collections and items, many improvements and tests for nice html output from kmail composer (not akonadi related), ate pizza and schnitzel (you understand that the location here is not located downtown Berlin and we have to deal with what we got).

I worked on the widget you get when you want to add a new resource. We switched from a boring KMenu to a shiny widget with iccns and descriptions we had already. It needed some love, and I gave it. I added a quick search widget in kdelibs which operates on a proxymodel, so you can quickly find the resource that you want for example.

Oh, and Thomas tried for ages reproducing a bug in the kmail-soc branch, but that is not akonadi related. Ingo is working on some code to create a shared outbox, messages dropped in there will be automatically send and placed in a send item folder. Igor worked on his testing framework, which will get more space on this blog tomorrow.