31.01.
    - indicate the command prompt has focus
    - added detection of changed OSM files
    - implemented get-info command
    - started working on the error reporting func.
02.02.
    - implemented MailService
    - implemented AppDiagnostics
    - added error reporting form, but it still needs to be beautified
    - support for polygons/polylines consolidated from relations
04.02.
    - solved the problem: why is footway drawn ABOVE residential road?
        - it's because the footway feature is defined AFTER the residential road
    - fixed: bug with form disposing        
    - if a way is used in a relation, it should be ignored elsewhere
        -written tests for this        
05.02.        
    - TODO: the rules and features should be specified in the reverse order
        - from the most important to the least important
    - TODO: how to solve layering problem?
 
 
 
- TODO: beautify error reporting dialog
- TODO: find an icon for Maperitive
- TODO: implement multipolygon polyline rendering
    - TODO: write tests for multipolygon rendering

This is an excerpt from Maperitive’s Todo.txt file. I use it as a log of the stuff I did for the current day and also as a “database” of the tasks I still have do. On various projects during the years I used Trac, Bugzilla, on Kosmos I used ToDoList for a while, but nothing beats the simplicity of a text file.

The history log is a recent “invention”: since Maperitive is a pet-project, the time allocated to it is very unevenly distributed – sometimes I do a lot of work in a single day (usually on weekends without find weather or hangovers), but then I have to leave it untouched for several days. So often it happens that I forget what I was working on – and this history log helps me to quickly refresh the memory. Also, it’s a good psychological tool: I take a look and the log entries and see that some work has actually been done and I’m (slowly) progressing towards the first release.

The added benefit is that I can copy&paste these log entries into SVN commit comments. And of course, Todo.txt is kept under the source control like the rest of the code.