As always, after larger changes, the chances are high that one or the other bug sneaks in 🐜

This is also true for v3.37 of OpenTodoList, so we’ll today release v3.37.1 to fix those issues.

Changelog

• rpdev/opentodolist#472: In the previous release, it was not possible to add new accounts 😱 This is particularly bad for new users (existing users of the app probably wouldn’t even have noticed). Still, this is a super important thing to get fixed!
• rpdev/opentodolist#467: Another very bad bug that needed to get ironed out. The main window of the app would not show up on Windows. This, as well, is fixed in this release.

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.

August, summer time and - of course - time for another release of OpenTodoList!

We have to admit, also this months list of changes is not too long. This is partly because there was only limited free time we could spend on the app. And partly, because we started something brand new (if you are curious: Head over to GitLab, there you can find the new project’s sources already - fancy images and a separate website are coming soon, promised).

Anyway, its still worth a new iteration of OpenTodoList, so let’s have a look what made it in this time:

Changelog

• rpdev/opentodolist#455: OpenTodoList is now around for several years. In this time, there was a lot ongoing also in the underlying framework the app is built upon (which is Qt and QML for writing the user interface). In this release, we took the time to clean up a bit in our GUI code. For you, this should vastly be transparent. The most notable change is, that we switched to Google’s Material Design Icons (previously, we used FontAwesome, which, however, became a bit more difficult to use in non Web Apps in recent versions).
• rpdev/opentodolist#458: Another minor change is, that the app now targets Android 11 by default. This is more a technical thingy and shouldn’t bother you too much, either. Still, this is the house keeping that we have to do as well 🧹

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.

Hi everyone! Yes, we know, it’s not quite beginning of July, so a new version of OpenTodoList is more than overdue. And while we were not able to put all the nice stuff we planned into this release (sorry - but, we were way too busy 😮) this release still comes with some really nice and useful new features!

Changelog

• rpdev/opentodolist#436: In OpenTodoList, you can put due dates on lots of items times. This includes - of course - todos. But you can also put dates on the items directly within a library (i.e. todo lists, notes and images). Within the library, you can also sort items by their due date - which is nice. However, what if you have a todo list without a due date but which contains todos that in turn have some? In this case, todo lists not inherit their due date from the todos contained within them, so they will e.g. appear on top of the list when sorting the contents of your library by due date.
• rpdev/opentodolist#434: Another very interesting enhancement is copying of items. You can now finally create copies of items within a library as well as of todos. Copying happens recursively, so if you e.g. copy a todo list, the copy will have copies of all the todos and tasks within these todos as well. And most importantly: This also works across libraries. So if you have e.g. a local library but want to switch to using one that is synced with e.g. your NextCloud, you can now create a new library and then simply copy over your existing items to the new one!

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.

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).

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? 😉

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.