A couple people now have inquired about the scripting with sqlite I mentioned on the last TechShow. A good example is a script I am using to track my time and tasks for the day which at work. The boss wants to be able to show that we are working on different things and what kind of time we are spending on different tasks so he asked us to keep track. I think most people just use a spreadsheet, but I started keeping notes on things in a text file that I could ultimately search through for information as well, and tracking my time there seemed a logical idea. After a few times of accidentally killing my vim session without saving my updated notes and time I decided I had better come up with a better solution, however, I wanted the solution to keep updating my original file in it’s original format. I decided on using sqlite to keep track of things just because this kind of application screamed for a database backend and sqlite is so small and easy to get going. The resulting script, tl, short for timelogger is a dumpy little thing in constant rewrite for new features that I have been using for quite some time now.
What you will see in the pic are the two output formats. The first is the format of my original timelog file that I wanted to keep using. This is also the one I email to my boss with the daily updates. The other is a more time-verbose listing. It lists the day chronologically instead of summing time per task like the first.
Although I have been using this and it works fine as it is, I love getting new ideas and requests from the OpenSource community as well, so check it out, play with it a bit and let me know what you think!