- We have a new filter overlay. We opted to avoid the inline searchbar entirely, and are using the overlay to display it instead.
- We try harder to display all search results and not artifically limit it. This was especially problematic because we don’t sort the search results before the limit, meaning we could end up loosing very relevant search results (such as recent mails).
- The composers html switch is gone. Instead we simply always offer the buttons to apply formatting, together with a button to remove all formatting for plaintext instead.
- Rémi landed his storage improvement patch which shaves off a cool ~15% of storage requirements. This also helps performance because smaller db mean less data to load into memory. This was followed up by fix for a performance regression caught by the CI.
- The Kube icon is now available in all necessary sizes to make it look good on Mac.
- Important emails are now indicated in the maillist.
- The default settings of the GMail account have been fixed.
- There is finally a separate login and email address field in the IMAP account configuration.
- We have a new website at kube-project.com where we now also offer the nighlies. These are now real nightlies that are automatically updated if all CI checks pass.
- Prevented multiple flatpak instances at the same time as this does not currently work properly.
- Last but not least, there’s progress on the Calendar.
More information on the Kolab Now blog!
“Kube is a modern communication and collaboration client built with QtQuick on top of a high performance, low resource usage core. It provides online and offline access to all your mail, contacts, calendars, notes, todo’s and more. With a strong focus on usability, the team works with designers and UX experts from the ground up, to build a product that is not only visually appealing but also a joy to use.”
For more info, head over to: kube-project.com
8 thoughts on “Last week in Kube”
Is there a place where I can leave wishes or other thoughts about kube? I just got it to run the first time. GREAT. But I am on a kde Neon system and I notice that the colors of Kube don’t integrate with my system colors, I would like very much to be able to toggle off the threaded view and last but not least I would like it if attached images would be shown inline. Thanks and keep up the great great work!
We do our planning via https://phabricator.kde.org/project/view/43/
While you are welcome to voice your thought and wishes, please note that we are working with very limited resources, and really have to choose where we spend them. We thus for instance decided that we would not do system theme integration in favor of a consistent look and feel accross platforms. It’s clear that this is a trade-off, but we’ll stick with that for the time being.
Similarly we’re also trying hard to avoid all options, and work with one solution that fits “most” users. It cuts down on development time, maintenance and keeps the product simple.
It’s clear that this is not for everyone, but I believe it’s what we have to stick to, at least for the time being.
Anyways, we can use all the input we can get to find the best middle ground, and over time, I’m sure, we’ll also improve on the customization part.
One of my favorite projects, keep the good news coming! 😀
I’m running a local instance of a Kolab Server. I have not been able to figure out how to configure kube to connect to it…? With kontact I have a bunch of configuration possibilities, yet with Kube it’s quite “minimal”… how to get it to work?
It is quite minimal, and in places it’s overly minimal…
I don’t know what the problem is, but normally you would just setup an imap account and point it to your server.
You can also edit the configuration files directly if that helps, and just for reference, here’s how I setup my testaccount with a script:
I really do feel strongly that:
1) Replies should be placed above the quote not at the bottom – this is common to most email clients including Gmail, Outlook.com, Fastmail and though the Kolab Web Client places replies below the quote, it allows you to make the change which I opted to do 🙂
2) Most recent messages should be at the top of the thread, not bottom. Also common to most other clients 🙂