Releases: projecthamster/hamster
v3.0.3
After a long hiatus and slow development, finally a hamster release
again! This version contains some usability fixes and makes hamster run
on newer systems.
Starting with this release, the hamster project also provides flatpak
builds of all releases (and also of git development versions). This is
now the recommended way of installing hamster, if your distribution does
not provide (up-to-date) packages.
One notable change is the parsing of the hamster cmdline (the
"activity@category, description, #tag, #other tag" string when you enter
or edit an activity as a single string), which is a bit simplified, but
no longer accepts everything it did before.
In particular:
- Remove the need for using a double comma to start the description,
a single comma can be used instead. Using double commas is still
allowed for compatibility. This does mean that a comma can no longer
be used in the activity or category. - The tags part must now be separated by a comma (previously, tags
could be appended directly to the activity, category or description.
This allows using # inside activity, category and description
(without needing a double comma to force a possibly empty tags part
at the end). For compatibility, the tags part can also be separated
by a double comma. - Simple #hashwords are now extracted from the description as
additional tags automatically (they can't start with numbers and
can't contain spaces, but those can still be written in the "tags
part" after a comma). This allows writing more natural descriptions
with embedded tags, like Coding, fix #bugs in #hamster. - Limitations on the fields are more consistent. All fields can now
contain any character, except:- The activity cannot contain @, since that would start the category.
- The activity and category cannot contain a comma, since that would start
the description. - The description cannot start with # or contain the tag separator
(one or two commas followed by optional whitespace followed by
a hash, e.g. , #), since this would start the tags part. - Tags in the tag part cannot contain a # or , (since that would
look like the start of the next tag). - Tags in the description part must start with a letter (upper or
lowercase a-z) and cannot contain whitespace.
Additional changes are:
- A number changes to the overview screen:
- Add daily total rows. (PR 596)
- Remove lines previously shown for days without activity. (PR 650)
- Refactor the range selection dropdown, preventing a problem where it would
not be shown on systems using Wayland and some other systems. (issue 639,
645, PR 647) - Do not periodically scroll to the top, only when displaying a new
set of facts.(issue 594, PR 648) - Fix overlapping texts with wide fonts (issue 698, PR 699)
- On Wayland, fix the popup below the tag field when editing activities
and the time field in the preferences window. (PR 652) - Fix exception when calling the dbus UpdateJSON method with a string
argument (issue 671, PR 672). - Fix the start date picker in the update/add activity window. (issue
590, PR 674) - Allow resuming last activity with ctrl-space (issue 595, PR 678)
- Added croation translation (PR 709)
- Fix running on Python 3.11 by removing call to deprecated
bind_textdomain_codeset
gettext function (issue 715, PR 715) - Fix running on Python 3.12 by updating the waf build system to 2.0.26
(PR 732) - Improve HTML export:
- Preserve newlines and special characters (PR 704)
- Make checkboxes work (PR 665)
- Updated and improved flatpak packagaging (issue 123, 456, PR 321, 111, 333,
610, 685) - Rework handling of tags in the cmdline, see below for details (issue
334, 657, PR 663) - Stop using pyxdg, GLib could already give the same information about
XDG directories (PR 727) - Minor updates to documentation (but far from complete for now)
v3.0.2
This release primarily fixes an off-by-one-day error in the CSV export, which could lead to extra data in exports (#576).
Note that the 3.0.x releases currently still have some rough edges resulting from some refactorings and features in progress. If you're happy with version 2.2.x, you might not want to upgrade just yet.
Changes in 3.0.2
- Switch from deprecated xml2po to itstool for translating help files
(issue 583). - Fix off-by-one-day error in CSV exports (issue 576).
- Support Python3.5 again, this was >= 3.6 (issue 582).
v3.0.1
v3.0
There was significant progress since v2.2.2.
Yet it would require more polish, and some functionality is in transfer (#493).
So users happy with their earlier version should wait for the next release.
It has been one year since last release, and there's the ubuntu LTS train to catch (still looking for a packager...).
Lots of files changed, so it is advised to uninstall in the previous version source tree.
NameHasNoOwner
is a known symptom for stray files.
Summary
Thanks to all contributors (either code or feedback) !
If a PR is linked to an issue, only the issue is listed. In case of leftovers, please comment over there.
Commits details, split in parts for clarity (+github display limit of 250 commits exceeded):
part 1, waf upgrade, part 2, hamster rename, part 3, part 4
v2.2.2 - python3 < 3.6 compatibility
Summary
Thanks to all contributors (either code or feedback) !
Commits details
v2.2.1 - start clone (resume activity)
Summary
Relevant issues
Thanks to all contributors (either code or feedback) !
Commits details
v2.1.1 - python3 migration
Migration to python3
and minor usability fixes
Thanks to all contributors !
Hamster 2.0-rc1
This release candidate marks the transition to Gtk3, and includes all the other feature additions and bugfixes that have been submitted since then and are too countless to list here. Thanks to all the contributors!
Please check README.md for the current dependencies.
You can also try the attached Debian package which was built with checkinstall
and should probably work on current Debian and Ubuntu versions. It doesn't follow the Debian packaging policy so you might get a warning when installing it.
Hamster 1.04
This version just packs all the contributed bugfixes of last 12 month (there
were just a few)
- bugfixes around talking to the notifications daemon
- updating tags list in prefs wasn't doing anything
- in some cases activity updates were failing when tags where provided