Crispin Flowerday

I seem to have a love, hate relationship with evolution. I do like the emailing interface, but it just seems so full of bugs, my most annoying ones at the moment are:

• It crashes picking up my work email (not a problem as I’m on holiday at the moment) – Bug 314199 (Fixed apparently)
• The preferences dialog has a really annoying resize when it appears – Bug 272967
• I can’t find the UI to configure the weather calendar
• It randomly seems to lose the paste buffer when composing emails – Bug 313430 amongst others
• It doesn’t filter for SPAM in unselected folders until you click on them – Bug 257730
• Why if I deselect the “Weather calendar” plugin does “Weather” still show up in the calendar list?
• It fails miserably to appear on the right workspace loaded from a saved session – bug 224608
• Spawning a second instance of evolution doesn’t clear the startup notification prompt when the window appears – Bug 271851

I’m seriously amazed that any companies roll this thing out as standard, it just doesn’t feel ‘polished’

Recently I upgraded to Breezy, which uses gcc 4 by default. Libxml2 uses a type called xmlChar everywhere, which handily is an unsigned char. Previous versions of gcc seems quite happy at silently casting from a char* to an unsigned char*, but Gcc 4 complains. In Galeon, we build with -Werror (only in maintainer mode), the combination of this meant that Galeon failed to build.

The solution, do through and add casts to xmlChar* everywhere, which ended up as about 250 different places. That was one of the most boring things I have done

I’m a twenty something Software Engineer, working for Zeus Technology. We write a Traffic Manager, and a Web Server, both high performance, highly secure products. Hence I have an indepth knowledge of HTTP and SSL (I basically maintain our high performance SSL server and client stack).

In the GNOME world, I do some patches for Galeon and Epiphany. Recently I have attempted to write a Mono extension loader for Epiphany, but got held up by the distinct lack of documentation for embedding mono in applications (especially w.r.t object lifetimes).