Lightweight, cross-platform and simple to setup timetracker. Similar to hamster but uses about 10MB of RAM and has a small quantity of dependencies.
I used hamster timetracker for my projects for years, but lately it disappeared from the debian repositories. I downloaded their latest version from github and it was not working well. After trying their other alternatives it was still not working well, so I decided to build the 'D-Tracker'.
My focus here is to:
- Implement the main features I use regularly.
- Reduce the number of dependencies and build steps so it is easier to make sure the application will still be easy to install in the future.
- Have a small resources usage so I can have it open all day without thinking about it.
- Be cross-platform so it works in more machines.
Release 1.0:
- Start task
- Stop task in progress
- Edit the start and end time of an individual task
- Associate a task with a project
- Export filtered tasks to XML with the same format as the hamster timetracker
- Listing of tasks per range of days
- Project/Task Statistics by range of days
- Autocomplete in task creation
Release 1.1:
- Select themes
Release 1.2:
- Command line client
Release 1.3:
- Remember last filtering range in overview window
- Simpler date range navigation in the overview window
Release 1.4:
- Periodically remember the currently active task
Release 1.5:
- Allow the copy of the tasks in the totals window to the clipboard
To run the application use the most recent release in the releases page.
- Archlinux AUR - https://aur.archlinux.org/packages/d-tracker/
You can download the latest binary here.
The application is self-contained in the folder so if you just want to run it there execute the run.sh
file.
If you want to install it to the system run the INSTALL.sh
. When installed in the system and started, a database will be created inside the ~/.local/share/d-tracker/
folder.
To uninstall run the UNINSTALL.sh
command. It will remove the whole application but still keep the database, so you don't lose your data in case your want to re-install it later.
The dependencies in the dependencies list are bundled within the repository and will also be compiled. In order to build the project from source you will need the following packages: automake
, libtool
, libx11-dev
, libxft2-dev
, libxext-dev
, libxxf86vm-dev
and libdbus-1-dev
.
To run the application self contained in a single folder run the following command and check the build/ generated folder.
make
To install the application in the system run:
make
sudo make install
To uninstall the application from the system run:
sudo make uninstall
You can download the latest binary here.
The application is self-contained in the folder so you just need to run the d-tracker.exe
file.
The dependencies in the dependencies list are bundled within the repository and will also be compiled.
My development environment is in Archlinux and Debian so I cross-compile the application. To compile the windows version you will need to have installed the mingw-w64
package. Then run:
make release_windows
After running the command, the self contained version of the software will be built in the build/
folder.
D-tracker has a cli, d-tracker-cli
that provides the following commands:
list-today-tasks List today tasks
list-tasks List tasks between a time range
list-projects Lists the projects available in the database
delete-task Delete a specific task
add-task Add a new task
edit-task-time Edit the time of a specific time
edit-task-description Edit the description of a specific task
edit-task-project Edit the project of a specific task
export-today-xml Export today tasks to a xml file
export-xml Export tasks in a time range to a xml file
export-today-csv Export today tasks to a csv file
export-csv Export tasks in a time range to a csv file
stop-in-progress Stop the current task in progress
If you are interested in improving d-tracker by improving stability, adding new functionalities, plugins, themes or other things check the development section.
To run the tests you will need busted.
Note: The tests will create and remove the database inside the build folder, be careful to not run the tests with important data there.
With that just run:
make test
The dependencies are in the external folder.
- luajit - Used as scripting language to implement the application.
- lsqlite - Contains the database and lua wrapper to communicate with it, so we can store the application data.
- date - Used for parsing and handling of dates.
- tekui - Used to implement the whole UI.
- LuaFileSystem - Used to list the folders when exporting the tasks to XML.
- freetype2 - (Only for X11) Used in the render of text and fonts in the tekui lib.
- argparse - (For the cli) Used to parse the command line options.
- libclipboard - Used in the copy_totals plugin to interact with the clipboard.
A devlog for the development until the version v1.2 is available in here.