Kalendar v0.2.0 is out now, adding drag-and-drop, improved calendar management, and lots of bug-fixes — Kalendar devlog 22

A week has passed since our first release and we are back with another one! We’ve worked hard to go through your bug reports and suggestions, and thanks to these we have a new version of Kalendar that is more stable and powerful than ever.

Note: Kalendar is still under heavy development. You’re free to poke around and try it out, but it is not yet final software! If you want to contribute to its development, join us in Kalendar’s Matrix room.

Our 0.2.0 release

While we are excited to have you try Kalendar, please not that 0.2.0 is still an in-development release and that there will be bugs and missing features. We want your feedback — especially bug reports! These will help us improve Kalendar as much as possible before releasing 1.0.

It is now in the hands of distribution packagers to add Kalendar to their repositories. The most up-to-date and unstable version of Kalendar will continue to come from our git repository, and some users have gone ahead and started packaging builds of Kalendar coming straight from our master branch.

We hope you enjoy using Kalendar as much as we enjoy making it, and look forward to what you have to tell us about it!

Now, here’s what’s new this week:

Drag-and-drop incidences to change their times

!147: Add drag and drop to change incidence start times (Claudio Cambra)
Commit 95b2a5f5: Dragged incidences now correctly return to where they were when dragged into non-droparea space (Claudio Cambra)

Another highly-requested feature has been added to Kalendar: you can now drag-and drop editable incidences in your views to change their times.

This feature has been added to all the calendar views. Both the month and schedule views let you drag and drop incidences onto different days and thus change the start date of your dragged incidence, while the week view offers more granularity by letting you set your incidence start time to the nearest quarter-hour.

Manage and customise your synchronised calendars

!148: Add menu with calendar editing options (Claudio Cambra)


We have also added a new context menu that you can invoke by right-clicking on your synchronised calendars in the sidebar. This context menu provides a number of new actions that let you easily manage your calendars straight from Kalendar.

  • ‘Edit calendar…’ invokes a properties dialog that lets you set an icon, name, and retrieval (sync) settings for this calendar
  • ‘Update calendar’ lets you immediately refresh the calendar and pull new changes from the calendar source
  • ‘Delete calendar’ is… self-explanatory
  • ‘Set calendar colour…’ lets you change the calendar’s colour without having to go into the settings

Usability tweaks and visual improvements

Commit 2a7db762: Can now press enter when delete dialog open to quickly delete (Claudio Cambra)
Commit ab0b5bd9: Completed tasks now have strikeout across views (Claudio Cambra)
Commit d06eed8f: Add number of tasks left to complete to filter header (Claudio Cambra)
Commit 53b7cfdd: Completion sliders now have highlight colour of parent collection (Claudio Cambra)

We’ve made some things faster and clearer.

Incidence deletion, for instance, now responds to the Escape and Return/Enter keys. So if you bring up the dialog to delete an incidence, you can rapidly dismiss it by either pressing Escape or quickly delete by pressing enter.

Regarding tasks: these are now more clearly marked as completed throughout calendar by appearing with strikethrough text across Kalendar’s calendar views.

In what is potentially an anxiety-inducing addition, we have also added the number of tasks to be completed to the tasks view’s header. This should let you know how much stuff you have left to do, which should help you panic a bit more!

Lastly, we have tweaked the completion sliders in tasks to have the same colour as the task’s parent calendar, helping the incidence info section feel less incongruent colour-wise.

Bug-fixes and small changes

Supporting us

Is there anything you’d like to see added to Kalendar? Get in touch! I’m @clau-cambra:kde.org on Matrix.

If you want to support Kalendar’s development, I strongly encourage you to donate to the KDE community. These donations help us keep our infrastructure running, including our GitLab instance, our websites, and more. You can donate at https://kde.org/community/donations/.

9 thoughts on “Kalendar v0.2.0 is out now, adding drag-and-drop, improved calendar management, and lots of bug-fixes — Kalendar devlog 22”

  1. I don’t want to use Kalendar because when I try to subscribe an online .ics calendar, Kalendar require Akonadi.

    Akonadi will spawn a mysql/mariadb in background by default. This is too bloated for me.

    If the calendar doesn’t require an online account, cannot it be more simple, like save to a local txt/json file?

    1. Short answer: no.

      Long answer: Akonadi handles pretty much every “transaction” that occurs between what you do in Kalendar and the data that gets written to both your local calendars as well as to whatever online calendars you are using. Akonadi is integral to managing how events and tasks are stored, retrieved, and presented to Kalendar.

      Regarding bloat: not sure what you mean here, as MySQL + Akonadi + Kontact in the background takes up around 499.4 MBs of RAM, which is around or below what other calendar/email/contact management suites like Mozilla’s Thunderbird and GNOME’s Evolution take up. Hell, the web versions of GMail and Google Calendar take up 520MBs of RAM together!

      1. Well, no. I have hundreds of thousands emails in my work Inbox and Akonadi sometimes even eats all of my RAM until I restart it (sometimes eats all my 12GB ram, maybe some memory leak). Kmail (minimum 2GB of ram, probably because of the big number of emails) hangs a lot when going from folder to folder with a lot of email. And with upgrading databases on the system Akonadi sometimes just brakes down and corrupts the databases and I need to resync everything all over again. And it pains me that I can’t use Kmail, but you guys have to understand that Akonadi is resource hungry and Kmail also, when it comes to big number of emails. I quit using everything Akonadi related because it brought me more problems than solutions. Looking at this app and want to use it, and the thought in my mind is “It needs Akonadi? Well, I’m not using Akonadi again, guess I won’t be using it. Bummer”.

  2. A am so exited that you take this on you! Great job!
    Imagine you go on in this pace. Than you could do a re-write of the KDE e-mail app as well.
    On the basis of Kube Mail or Trojita and using Kirgami.
    It takes ages and a lot of experience to get Kmail working and even then is always unstable and unpredictable.
    I think people should not put energy in Kmail.

Leave a Reply

Your email address will not be published. Required fields are marked *