Martin Höher Reading time ~4 minutes

Very punctual - on the 1st of April - a new version of OpenTodoList is available 🎉

This release has a nice mixture of both new features as well as fixes throughout various parts of the app. That should make the app way more enjoyable.

Changelog

  • rpdev/opentodolist#414: There was a nasty little bug 🪲 which occurred when deleting a library from the app and immediately adding it back. In this case, the library would not get synced - one had to restart the app for the initial sync to take place. Well, this is past now!
  • rpdev/opentodolist#429: A task is a task and will always remain a task. Well, not so true anymore for OpenTodoList 😉 You can now promote tasks and make them todos.
  • rpdev/opentodolist#430: Did you ever add back a larger library on a new device? You might have noticed that the initial sync could potentially take quite a while (as larger libraries tend to consist of a lot of small files). Especially if you belong to the impatient - rejoice! The app now shows the progress of the sync operation.
  • rpdev/opentodolist#425: Another bad bug: Sometimes the app would hang when trying to quit it. That was due to incorrect handling of the sync database - which was not properly closed and hence could cause the app to not properly terminate. Fixed in this release ✔️
  • rpdev/opentodolist#187: Sometimes, a sync operation fails. This can have various reasons - there could be an intermittend network error. But maybe, also the password used to connect to the server was no longer correct. In the past, such errors were only visible when you had the library which failed to synchronize open. However, when you would have another library open, you would not get a trace of that issue. This has been fixed now, by treating sync errors as application problems. Such problem reports are visible regardless of whether or not you have a particular library open.
  • rpdev/opentodolist#410: There was a bug which prevented the user from properly scrolling in the Note page when the content was longer than the window or screen size. That issue is now fixed as well!
  • rpdev/opentodolist#409: Let’s continue with bug fixes: On iOS, the copy and paste actions were not available. In addition, the app would probably be displayed too small (actually, this scaling issue was the cause for the missing copy and paste functions). This version of the app fixes this!
  • rpdev/opentodolist#417: With the last release, we enabled the cmake based build of the app again - but not yet for all targets. With this release, the Snapcraft build is now also back to using cmake. In addition, we now build the app directly from within our CI/CD pipelines, which should reveal issues for this targer way earlier than in the past.
  • rpdev/opentodolist#428: When you (re-)open the main window of the app, we now trigger a sync of all libraries immediately. This ensures that you get the latest version of your libraries’ contents whenever you return to the app, e.g. by showing again the activity on Android or bringing back the window after minimizing the app to the system tray on Desktop systems.
  • rpdev/opentodolist#427: We already talked about cmake. The previous main release v3.32 also built the Android version using cmake. Unfortunately, there was an issue and we had to revert to qmake, releasing an intermeditate v3.32.1. This release fixes the cmake build for Android, so it is working as expected now.
  • rpdev/opentodolist#413: Most people probably use OpenTodoList to store notes and todo lists. But you can do more, for example you can add images to your libraries or add attachments to most items. However, a bug sneaked in, which would prevent such items from being included in the sync of a library. This is fixed now, so any additional files will get up- and downloaded again. Please note, that if you are missing some files, you might have to remove the affected library and add it back to the app.
  • rpdev/opentodolist#422: OpenTodoList depends on several libraries (apart from the underlying Qt framework), which are - for the convenience of developers - included in source form in the repository. Also, when building, the app would always build these libraries from source as well. This is, however, bad under certain circumstances. In particular, this made packaging the app for some Linux distributions impossible, as they mandate that if there is a library available in the main repositories, it must be used instead of a private version. We address this in the cmake build, which now can be configured to build the app against system versions of the required libraries - either for all of them at once, or you can finetune which library shall be used in source form and which shall be used from the system installation.
  • rpdev/opentodolist#423: And last but not least… with the previous version, installing the app on Arch Linux from AUR could potentially fail, if you had the QtKeychain library installed as well. This is now also fixed, so installation from AUR should work in any case.

You can now promote tasks and convert them to todos - this makes re-organizing your work in OpenTodoList way more flexible!

Downloads

  • Please find the download links for major platforms on GitHub.
  • For Android, the release is available via Google Play.
  • For iOS, the release is available via the App Store.
  • If you use snap, you can install the app from the snapcraft.io.
  • If you use flatpak, you can install the app from Flathub.
  • For Arch based Linux distributions, you can install the app from AUR.

Known Issues

There are currently no known issues. If you encounter any issues, please file a bug report in the bug tracker.

Martin Höher Reading time ~1 minute

The last release of OpenTodoList brought again some under-the-hood changes. And of course, a mean little bug managed to sneak in 😠 So, here comes an intermediate bug fix release of the app:

Changelog

  • rpdev/opentodolist#426: On Android, HTTPS connections were broken on at least some devices. If you have an already existing library, this one simply won’t sync anymore. Adding new libraries even didn’t work out at all! We still have to find out what causes this (a first attempt at fixing this with the new cmake based build didn’t work completely) - so for the moment we revert back to using qmake for building the Android releases of OpenTodoList.

Downloads

  • Please find the download links for major platforms on GitHub.
  • For Android, the release is available via Google Play.
  • For iOS, the release is available via the App Store.
  • If you use snap, you can install the app from the snapcraft.io.
  • If you use flatpak, you can install the app from Flathub.
  • For Arch based Linux distributions, you can install the app from AUR.

Known Issues

There are currently no known issues. If you encounter any issues, please file a bug report in the bug tracker.

Martin Höher Reading time ~3 minutes

Once again, we are well into March - over time for the next OpenTodoList release 🕓

While the list of changes this time is not overly long, it still is interesting and - as so often - should help ready the app for accelerated development in the future.

Changelog

  • rpdev/opentodolist#325: This is definitely the issue we spent most time on this release. And if you followed the release notes of OpenTodoList closely, you most likely will have a kind of déjà vu. Yes, we once again tried to port the app over to cmake as a build system. This isn’t the first time - and currently, the qmake based build still works fine. However, Qt, the framework OpenTodoList is mostly build on, migrated to cmake as its main build system with version 6 (to which we hopefully will upgrade soon). Using cmake would bring a lot of advantages over qmake, so it anyway makes sense. Now, with Qt supporting cmake more widely and on more platforms, reviving the cmake build for OpenTodoList was the right time. We still need to look into two targets - iOS and Snap - where for this release qmake is used. As soon as we have them covered, cmake will be used for all official releases of OpenTodoList.
  • rpdev/opentodolist#415: Upon a release, GitLab and GitHub create source tarballs automatically, allowing you to download a snapshot of the sources of the app at the time of the release. This is sufficient for a lot of projects, but currently, due to the use of git submodules and how they are included in the app, the auto-generated tarballs were not suitable to build OpenTodoList from these. We fixed this, but creating own tarballs, containing also the sources of the included sub-modules. That way, you now should be able to build the app also from the provided tarballs attached to the releases on GitHub!
  • rpdev/opentodolist#407: In the library page, when some of the entries had long titles, they were just cut off. This wasn’t quite elegant, so we had to change this. First, as titles get longer, the font size is decreased a bit to fit the title into the item. If the title is even longer and we would need to decrease the font size below a certain limit, we show an indication that the item title is stripped and - when hovering the title with the mouse cursor - show the full one in a tooltip.
  • rpdev/opentodolist#408: This one especially hit users on some Android devices, but also might be known to some users on other platforms as well. OpenTodoList prefers using the Roboto or Noto fonts for the GUI, falling back to any font the underlying system deems suitable if neither of them is present. This sometimes led to very strange fonts being used. We are now fixing this by including a copy of the Roboto font with the app - so it now should look nice on any platform, no matter of these fonts are included natively there or not.

Titles of items in the library page now intelligently reduce the font size as the title gets longer. If the font would get too small, the title is truncated - you still can see it via a tooltip by hovering the item.

Downloads

  • Please find the download links for major platforms on GitHub.
  • For Android, the release is available via Google Play.
  • For iOS, the release is available via the App Store.
  • If you use snap, you can install the app from the snapcraft.io.
  • If you use flatpak, you can install the app from Flathub.
  • For Arch based Linux distributions, you can install the app from AUR.

Known Issues

There are currently no known issues. If you encounter any issues, please file a bug report in the bug tracker.

Martin Höher Reading time ~1 minute

Time for another hot fix release!

This one is particularly important for Windows users, so in case you already updated and experience sync issues, please read on.

Changelog

  • rpdev/opentodolist#406: On Windows, when syncing against a generic WebDAV server, chances were that an invalid URL was generated by the new sync mechanism and hence, sync would fail. This is fixed now, so synchronizing your libraries against generic WebDAV should work again with this version.
  • rpdev/opentodolist#359: As a small gimmick, this release integrates a new feature which will be part of the next monthly release. In the settings, you can not specify a minimum size for items in the library view, so you can tune the size of the cards to your liking.

Downloads

Known Issues

There are currently no known issues. If you encounter any issues, please file a bug report in the bug tracker.

Martin Höher Reading time ~1 minute

It’s bug fixing time 😮

After yesterday’s release of v3.31, some issues have been found with the new sync code - it seems, it especially happens on Windows, but we cannot exclude that other systems are not affected.

Changelog

  • rpdev/opentodolist#404: There were some issues in the code, which might cause the sync to delete some files. For this reason, please upgrade as soon as possible to 3.31.1! If you sync against a NextCloud or ownCloud instance, you can always recover deleted files. Even if you don’t immediately miss items, check your trash can if there is an unusually high number of deleted files since you upgraded to v3.30. Note that earlier versions are not affected. The fixes are specifically for the new sync code introduced in yesterday’s release. So if you did not upgrade to that release yet, you should be clean.

Downloads

Known Issues

There are currently no known issues. If you encounter any issues, please file a bug report in the bug tracker.