This is a lightweight Gtk+ application designed to track time in a non-intrusive manner. The software aims to provide users with a hassle-free experience.
GTimeLog is a fantastic software tool that helps you keep track of your daily work activities. Once you arrive to work, all you need to do is simply start gtimelog and type "arrived". The software allows you to start doing some activity (like reading mail or working on a task). When you stop doing your activity, type the name of the activity into the gtimelog prompt. You can even use the same text if you make several entries for an activity. Simply use the up and down arrow keys to access history.
One key principle of GTimeLog is to name the activity after you've stopped working on it, not when you've started it. But of course, you can type the activity name upfront and delay pressing the Enter key until you're done. GTimeLog displays all the activities for that day and calculates the total time spent "slacking" and total time spent working. It also advises you how much time you still need to work to get 8 hours done for the day.
GTimeLog has two basic views. One view shows all the activities in chronological order with starting and ending times. The other groups all entries with the same activity into one and just displays the total duration. At the end of the day, you can send off a daily report by choosing Report -> Daily Report. You can use your mail program (Mutt in a terminal) to edit the report before sending it.
If you make a mistake and type in the wrong activity name or forget to enter an activity, GTimeLog stores the time log in a simple plain text file (*.gtimelog/timelog.txt). Every line contains a timestamp and the name of the activity that was finished at the time. You can add comments on the same line as well. However, make sure no comment begins with a timestamp. You do not have to worry about GTimeLog overwriting your changes since GTimeLog always appends entries at the end of the file and does not keep the log file open all the time. You do need to worry about overwriting changes made by GTimeLog with your editor, so make sure you close timelog.txt in your editor before entering any activities in GTimeLog.
One key principle of GTimeLog is to name the activity after you've stopped working on it, not when you've started it. But of course, you can type the activity name upfront and delay pressing the Enter key until you're done. GTimeLog displays all the activities for that day and calculates the total time spent "slacking" and total time spent working. It also advises you how much time you still need to work to get 8 hours done for the day.
GTimeLog has two basic views. One view shows all the activities in chronological order with starting and ending times. The other groups all entries with the same activity into one and just displays the total duration. At the end of the day, you can send off a daily report by choosing Report -> Daily Report. You can use your mail program (Mutt in a terminal) to edit the report before sending it.
If you make a mistake and type in the wrong activity name or forget to enter an activity, GTimeLog stores the time log in a simple plain text file (*.gtimelog/timelog.txt). Every line contains a timestamp and the name of the activity that was finished at the time. You can add comments on the same line as well. However, make sure no comment begins with a timestamp. You do not have to worry about GTimeLog overwriting your changes since GTimeLog always appends entries at the end of the file and does not keep the log file open all the time. You do need to worry about overwriting changes made by GTimeLog with your editor, so make sure you close timelog.txt in your editor before entering any activities in GTimeLog.
What's New
Version 0.2.4: N/A