QML GUI frontend for the hamster-lib timetracking backend.
This GUI front-end is the result of not finding a suitable replacement for the Project Hamster application on Windows. The hamster-cli Command Line Interface was used for a while until this project was started.
This project has no connection with the Project Hamster except for using the Python library provided by the project.
Since the hamster-lib is written in Python, Python was chosen as the language for the development. QML was chosen as a learning opportunity to get familiar with QML and QtQuick.
I have a strong C++ and Qt background but basically no experiance with QML nor Python. This whole project is seen as a learning opportunity but will hopefully be useful to some people.
Since the GUI is based on Python and QML there is no need to build the sources. All that is needed is to install the correct software, get the source and run the application. Although all development and testing is done in Windows, there is no reason why it should not work on other proper Operating Systems.
The following steps can be used to run the GUI:
C:\Progam Files\ should not be used. This is to prevent issues with Python in future.pip install hamster-libpip install PyQt5python hamster-qml.pyThe following terms are used in the application, they originate from the terms used by the hamster-lib.
| Term | Description |
|---|---|
| Fact | Event or work that is getting done. It has a start and end time, a category, activity and description. |
| Category | Category is the high level grouping that the work belongs to. For example this project, hamster-qml can be one. |
| Activity | Activity is like a subtask of the category, like develop or test |
| Description | The description can be a comment describing the work done. For example fixing some issue. |
| Ongoing Fact | Work or a fact that is currenlty in progress, it does not have an end time (yet). |
To log work, or a new fact, the activity must be entered in the 'Log work' edit field. The following format is required:
<time> [activity]@<category>, description
| Tag | Required | Comment |
|---|---|---|
<time> |
false | Time that the work started. Either one of the following formats are required. |
HH:MM - Absolute start time of the task, example: 08:00 |
||
HH:MM - HH:MM - Absolute start and end time, example: 08:00 - 09:00 |
||
-MM - Start time relative to the current time, example: -30 (started 30 minutes ago). |
||
| No time if the task starts at the current time, now. | ||
[activity] |
true | ‘What you are doing’ |
Any word without whitespace or special characters, example: development |
||
<category> |
false | Any word without whitespace or special characters, example: hamster. |
If no category is specified, do not add the @-character. |
||
description |
false | Short description of the activity if needed. |
If no description is supplied, do not add the ,-character. |
For a more complete description, read the docs on the hamster_lib here
If a fact is started without an end time, the work will be regarded as ongoing. As such it will be added to the 'Current work' edit field. This work can then be stopped or cancelled. If stopped, the current time will be used for the end time of the work. If the work is cancelled, it will be removed and deleted. Ongoing work will be remembered between application runs, for example when restarting the computer.
New work can be adde even though there is an active fact. When this happens, the current work will be stopped and the new work will be started. The end time of the work will be set to the start time of the new work.
On any of the tables showing logged work, one can double click on an entry to edit the work.