Caldav for Symbian^3

Initial Caldav support for the Symbian platform has been contributed and integrated into the organizer main codeline. For more info, have a look at the blog entry on the official Symbian blog

CalDAV support for Symbian: a contribution by Sun Microsystems

as well as the Symbian Foundation Wiki page:

Caldav for Symbian OS

Symbian^3 Preview

Symbian is open!

Four month ahead of schedule, Symbian OS is now fully open source:

http://blog.symbian.org/2010/02/04/symbian-is-open/

Hudson and CodeScanner

Being a great fan of Continuous Integration and the Hudson server, I'm using it to build the Organizer Package of the Symbian codebase on a regular basis to get reproducable builds as well as a good overview of the number of warnings, differences between compilers and a lot more.

To get even more info out of it and get some kind of a deeper overview on the status of the package right after a build without any manual interaction, I developed a plugin to be able to use the Codescanner tool within hudson.

CodeScanner is a static source code analysis tool for Symbian programs written in C++. Static analysis tools delve deep into code, exploring line by line for the sources of defects. CodeScanner is specifically for use with Symbian code. As well as identifying C++ coding convention deviations, CodeScanner identifies incorrect descriptor usage, cleanup stack errors, UID clashes, and other subtle problems that are hard to track down.

There are several exciting features available in the plugin:

• Build summary showing the new and fixed warnings of a build
• Several trend reports showing the number of warnings per build
• Overview of the found warnings per module, package, category, or type
• Detail reports of the found warnings optionally filtered by severity (or new and fixed)
  • Short messages is read from the report file
• Colored HTML display of the corresponding source file and warning lines:
  • Direct link to the warning line
  • Highlighting of single lines as well as line ranges
  • Highlighting of multiple line ranges per warning (different color for primary range)
  • Tool tip describing the warning message
• Failure threshold to mark a build as unstable
• Configurable project health support

For more information, installation instructions and how to use the plugin, have a look at the wiki page: CodeScanner Plugin

A huge thank you to Ulrich Hafner, author of several similar static analysis hudson plugins. The codescanner plugin uses his analysis-core classes as a base, this is were most of the magic happens. Using his work, this plugin was easy and fast to write.

Notes2 progress

While it has been quiet for a while in regards to further development of the Notes2 Module of OpenOffice.org Writer, there is now some nice progress in bugfixing going on.

Oliver Wittman started working on Issue 88070, which will expose notes/comments to the appropriate accessibility tool. This will further strengthen the implementation of the notes as well as of accessibility support in OpenOffice.org.

Caolan McNamara finished working on Issue 98634. Writer will now save comments attached to a recorded change as a regular note when exporting your document to Microsoft Word. Before the fix, these information were lost, as the doc format does not support these change comments.

Next I'll be working on some fixes for the internal layout of the notes itself when working with right-to-left languages to get the same quality there as with left-to-right languages.

I also noticed that the code for the Impress Notes is mostly the same code as the Writer class SwMarginWin and we could clean up and reduce a lot of code there. It would be probably a good thing to make SwMarginWin even more broad and move it to svx. Impress and Writer can then reuse the class from there.

What's your favourite and most annoying notes2 bug? If you have other ideas for improvement, let me know!