After the previous releases of the app rather have been bug fix and maintenance ones, this ones finally brings some cool new features.

Changelog

  • You can now re-order items inside a library via drag&drop. This allows you to put the items you are working most frequently with to the top of the page easily! rpdev/opentodolist#218
  • A progress value can now be set on todos. Until now, there was a progress indication derived from the number of open and closed tasks within a todo. Now, you can set a progress value manually, which overrides this computed one. rpdev/opentodolist#204
Reordering of top level items and progress values on todos

Downloads

Please find the download links for major platforms on GitHub. For Android, the release is available via Google Play.

Known Issues

  • There is a known issue with the cache DB used by the app (rpdev/opentodolist#214). When you installed e.g. a 32bit version and then change to a 64bit version, the cache cannot be opened and the app won’t work properly. To fix this, remove the previous cache directory manually before starting the app.

This version of OpenTodoList is rather a maintenance release. It bumps up the used version of Qt on most platforms to v5.11, for some even to 5.12. The most interesting change however is that the app is now available via Flatpak.

Changelog

  • The app is now using at least Qt 5.11.2 on all platforms we build relases for. On some platforms, we even use Qt 5.12 now. rpdev/opentodolist#209
  • APKs are now signed within the CIs. This means that the APK files can be downloaded and installed as-is without further manual intervention. This eases both testing of developer builds as well as releasing to the Google App Store. rpdev/opentodolist#211
  • There recently was a change in the tool linuxdeployqt which we use to create AppImages for Linux. This is worked around temporarily by using an older release of the tool in the CIs. rpdev/opentodolist#216
  • Last but not least, the app is now available on Flathub. This means you can easily install it on most Linux distributions via the flatpak command line tool or your favorite software store. rpdev/opentodolist#2159, rpdev/opentodolist#219, rpdev/opentodolist#220
OpenTodoList is now available on Flathub

Downloads

Please find the download links for major platforms on GitHub. For Android, the release is available via Google Play.

Known Issues

  • There is a known issue with the cache DB used by the app (rpdev/opentodolist#214). When you installed e.g. a 32bit version and then change to a 64bit version, the cache cannot be opened and the app won’t work properly. To fix this, remove the previous cache directory manually before starting the app.

This is again a release which took a lot of time - however, it is an important one. While there shouldn’t be a lot of user visible changes in, this release comes with quite some changes under-the-hood, improving the performance of the app dramatically. And also, the obligatory bug fixes are in.

Changelog

  • We integrated QLMDB as a cache for item data. On top, a kind of object store has been implemented, where most interactions are done via transactions executed in background threads. Long story short: For you as a user this means a much more fluent user interface. In particular when your libraries grow, you will notice performance improvements when switching between views. This change implicitly also fixes some minor issues like e.g. the app had to be restarted to apply the deletion of an item via a sync from the server.
  • This release comes with an important fix for Android users of the app. Creating libraries in the default location did not work on all devices. With this release the default location has been changed, which should fix this issue on all devices.
  • Another important step is that the app now moved away from qmake as its build system to cmake. The latter is much more flexible (at the cost of not being as deeply integrated with the Qt Creator IDE used for developing the app) and also makes it easier to integrate libraries which also use cmake for building.

Downloads

Please find the download links for major platforms on GitHub. For Android, the release is available via Google Play.

Known Issues

  • On Windows, make sure you have proper OpenGL support. The app strictly requires OpenGL to work. Most notably, when running within a Virtual Machine, chances are that starting the app will result in an error.

After a lot of monthly releases in the past, there has been no update since April 2017. However, no reason to worry. There’s a larger update in the pipeline, which requires some preparation in the form of a new library called qlmdb - a Qt wrapper around the lmdb C library, which is going to be used in a future version of OpenTodoList.

While most work went into bringing up qlmdb, there were also some bug fixes in the app, which now become available.

Changelog

  • There was a bug which caused the user interface to constantly be redrawn. This could significantly drain your battery on mobile devices and laptops. #201.
  • The process of setting up a new synchronized library has been improved. Before, when entering e.g. a wrong password, there was no indication that something went wrong. The Validate button simply wont vanish and the OK button never appeared. Now, there’s some better, visual indication to the user that something went wrong. #200

Downloads

Please find the download links for major platforms on GitHub. For Android, the release is available via Google Play.

Known Issues

  • On Windows, make sure you have proper OpenGL support. The app strictly requires OpenGL to work. Most notably, when running within a Virtual Machine, chances are that starting the app will result in an error.

It took a bit longer than usual, but better late than never: OpenTodoList 3.7 has been release! This version is all about cleanup of the graphical user interface spiced with some workflow changes.

Changelog

  • The app now uses the Material theme on all platforms. This makes it easier to create a consistent experience throughout all supported OSes and device types we run on. The downside of the change is that on Desktop platforms you no longer have your desktop’s color theme (where applicable), however, ensuring the app looks great with all (or even just most) color themes is quite difficult and would require much more time - which simple is not possible given that OpenTodoList is developed as free time project.
  • The above change goes hand in hand with a general cleanup of the user interface. This year, the app celebrates it’s fifth birthday already. There has been a lot of changes and re-iterations going on in these past years. As a result, the QML files which describe the app’s user interface were quite complex and - frankly - cluttered. With this version, the QML files are cleaned up and restructured in a more logical manner. This should help speeding up further changes in future versions. With the cleanup, the GUI has also been polished nicely.
  • When building for Windows using the Microsoft Visual Studio toolchain, OpenSSL is not downloaded during the build - meaning we can remove the remaining pre-build binaries from the repository; an important step to get F-Droid compliant.
  • Text inputs now generally wrap when entering longer texts. This makes entering text especially on touch devices much easier.
  • There is no longer a default Inbox: The inbox was intended to be the default library used after starting the app for the first time. However, there are no features making explicitly use of this. Hence, the Inbox is no longer created when running the app. When you used the app before, you can just delete the Inbox like any other library.
  • There was a bug showing update notifications: They were not shown due to a misconfiguration in the build system.
  • Libraries can now be renamed.
  • Item titles are now Markdown formatted everywhere.
The re-designed Material user interface in action.

Downloads

Please find the download links for major platforms on GitHub. For Android, the release is available via Google Play.

Known Issues

  • On Windows, make sure you have proper OpenGL support. The app strictly requires OpenGL to work. Most notably, when running within a Virtual Machine, chances are that starting the app will result in an error.