Hey everyone! Summer is here 🌞 - and as it’s just the beginning of the month, it is again time for a new release of OpenTodosList! Admittedly, the list of changes that went into this one is not as long as for the previous releases, but this doesn’t matter. First of all, we again have a nice mixture of new features and important fixes. And on top we have exciting changes in the pipeline, that hopefully should hit us in the next release, due beginning of July. But before that future release, let’s check out what went into today’s one:

Changelog

  • rpdev/opentodolist#448: Bug fix number 1 🐛 - under certain circumstances, it could happen that if you did some changes in quick succession (as ticking off several todos inside a list in a short time), due to the sync that is immediately triggered after the first change, the other ones get mystically discarded. We implemented some counter measures that should stop this from happening in the future!
  • rpdev/opentodolist#444: And bug fix number 2 🪲 - it seems that there are a lot of - let’s call them faulty - WebDAV servers out in the wild that do not report etags on the folder level. These etags are used to detect changes on the server efficiently - without them, clients need to issue in the worst case not only one but several remote queries to find out if some files have changed on the server and hence need to be downloaded. If a server did not report etags on folders, OpenTodoList would reject adding an account for it in the first place. However, if you are a user of such a service and had no choice to switch to another provider, this meant you were out of luck and unable to use OpenTodoList. This is no longer the case 🎉 At the expense of having to issue several HTTP calls, OpenTodoList can be used now also with such faulty WebDAV servers!
  • rpdev/opentodolist#446: Enough talk of bug fixes - as promised, this release also brings some new features. So let’s start with the first of them: When setting up recurrence for an item, you can now schedule it to recur yearly. 📅
  • rpdev/opentodolist#447: And while we are talking about recurring items - we did not only include yearly recurrence, but you can also set up items to occur every N weeks or month (similar to the recurrence every N days was already available in the app).
Starting with v3.35, you can set up items to recur yearly or every N weeks or months.

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.

It’s May, and while most of us probably still are eagerly waiting for our Covid vaccination, here’s at least a new version of OpenTodoList! 🎉

The list of changes that went into this release is quite long, and again, it is a nice mixture of both new features as well as ironing out nasty little bugs.

Changelog

  • rpdev/opentodolist#440: In OpenTodoList, you can attach files to most of the items. This is useful if you want to stick something like images or documents to e.g. a todo, so it is easy to look up the information from the item itself. When using the Snap version of the ap, though, opening these attachments unfortunately didn’t work. Until now 😉
  • rpdev/opentodolist#437: Another bug, this time a bit more scary 🕷 The app currently uses WebDAV to synchronize your libraries via arbitrary WebDAV servers. This usually works quite nice. However, when using e.g. Apache’s mod_dav on the server side to make a folder accessible for OpenTodoList via WebDAV, this triggered a bug in the underlying Qt framework. This version of the app implements a workaround, so that sync via mod_dav should work just fine!
  • rpdev/opentodolist#432: This is rather something internal, but for the records: Automatic uploading of the app to Snapcraft did not work. Well, fixed it ✔️
  • rpdev/opentodolist#418: This is another big step for us: The iOS version of the app is now also build using cmake 🥳 This finally makes cmake our default build system for all targets we officially support, so the next step will be to finally phase out the qmake based build. While this isn’t a user facing change, it makes maintaining the app significantly more easy for us.
  • rpdev/opentodolist#368: A smaller enhancement, but still good its now there: Strings in the Android notification are now translatable. 📜
  • rpdev/opentodolist#441: Another important workaround for this release. We received a report from a user, where, after attaching several (larger) files to items, the upload during sync would fail. In that user’s case, sync happened via NextCloud (and in fact it seems that this is a kind of NextCloud bug we triggered). However, we implemented a workaround on the client side, so the sync should work very reliably (hopefully also with some other servers that potentially might have the same issue - who knows 😄).
  • rpdev/opentodolist#431: This is a bit… well. We had to remove the Donate link from the app for the iOS version. The background here is quite simple: Apple does not want apps to use “custom payment”. On iOS, everything has to be routed through Apple’s own payment method. One can certainly argue if this is good or bad by Apple, but for us to be able to still deploy to the AppStore, this was the only way (well, we could of course also integrate Apple Pay, but this simply isn’t worth the effort, so we better spend the time on implementing some useful enhancements or fix bugs in the apps in the meantime 😉).
  • rpdev/opentodolist#420: Another internal thingy… we switched to a new branch naming. As git and platforms build around it (like GitLab) move away from wording having negative connotation (like master for the main branch), we also took the change to rename and also introduce better branching in general. Previously, all development happened on the master branch. Starting from this release, we are having two main branches: development is where the latest gratest stuff is developed. While this branch usually should be rather stable (thanks to our CIs), it still is rather something for the brave. Once we do a release, we merge to the stable branch and create a release from there. Also, in future, if a quick bug fix release is needed, this fix can be implemented directly on the stable branch. For you - as a user - these changes should be rather transparent, though.
  • rpdev/opentodolist#419: More cleanup… talking about our CIs: We also took the chance to clean up a bit. Over the years, a bit of clutter happened to gather in the CI definitions, so removing some stuff and streamlining was required.
  • rpdev/opentodolist#416: Not so important for direct users, but if you want o build the app, this now also got a bit easier. Well… or at least, better documented 🙃 The build instructions have been improved quite a bit and should now be way more useful if you plan to build the app yourself from source.
  • rpdev/opentodolist#370: No, we didn’t only clean up. Another useful and user facing change is, that the app now uses the KNotifier library for handling the system tray icon on some platforms.
  • rpdev/opentodolist#327: Did you ever, e.g. in the schedule view, accidentally mark a todo as done and didn’t know how to find it back? Then, this change will definitely cheer you up: There is now an undo operation (which you can trigger via Ctrl+Z or Cmd+Z) to undo such a mistake!
  • rpdev/opentodolist#442: When using the AppImage version of the app on a Wayland based Linux system, changes were that it didn’t work (meaning: the application window wouldn’t show up). We worked around this by removing the Wayland support for now - so the app uses XWayland on such systems by default). We hope to be able to enable the native Wayland support in a later release. Note that this only affects the AppImage version of the app. The snap doesn’t have direct Wayland support either. If you want to use native Wayland on Linux, you can, however, use the Flatpak version of the app.
  • rpdev/opentodolist#318: This is definitely the feature of this release! OpenTodoList now comes with a quick notes feature on desktop systems 🤯 The feature is optional, so unless you want to make use of it, it won’t stand in your way. You can bring up the quick notes editor either by right clicking the system tray icon and selecting the Quick Notes Editor option from there. Alternatively, you can go to the app settings, scroll to System Tray and enable the Open Quick Notes Editor in Click option. Then, clicking the system tray icon will bring up the editor as well. But, what is the Quick Notes Editor❓ That’s quite easy: It is a simple editor, where you can drop any Markdown text you like. The content of the editor is automatically saved - it will also survive restarting the app. So in the easiest case you can just use it as an intermediate store for some plain text of yours. But if you collected some useful stuff there, you can directly save the content of the editor as a note or todo list in one of your libraries. Neat, isn’t it? 😉
The Quick Notes Editor provides a neat way to quickly store some Markdown formatted text. Once you are done with the text, you can easily create a note or todo list from it.

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.

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.

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.

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.