New year, new Kube =)
- Setup a clearer structure for the application with “Views” as the highest level components (composer, conversation, addressbook, log, accounts).
- Made sure that individual views are self contained and can be launched using qmlscene. This is not only good for modularity, but simplifies the workflow when working on the UI.
- Improved the test and prototyping infrastructure: Blogpost
- A little investigation in where all the memory goes: Blogpost
- Added an extension mechanism that allows us to easily experiment with new views, without compromising the main application.
- Support to unlock kube from the commandline as a poor-mans keyring integration.
- A rather large cleanup of encryption related code used in the message parser got rid of over 1k SLOC.
- The encrypted/signed state of a mail is now properly visualized.
- A storage upgrade mechanism was added (Although upgrading for now means removing all local data).
- Large payloads are no longer stored externally but inline in the database. Tests have shown that this is not less performant, but improves the fault resiliency and simplifies the system.
- A first version of Xapian based fulltext search for local content just landed (Blogpost will follow).
- As always, a variety of bugfixes.
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.kde.org
6 thoughts on “Last week in Kube”
Great stuff so far – would love to see a Mac build.
Are you currently short-staffed as it’s noticeable that you are the only person making commits with a few thrown in from Michael every now and again. Do you anticipate this to change and thus ramp up development?
So far loving the minimalist look and feel of the client. UI is awesome, and so is usability
A mac build is high on the wishlist, and I’ll get around to it eventually. I’ll promise 😉
As you mention, there is indeed a lack of manpower, it’s not a small task after all. I anticipate this to improve some over the course of this year, but I doubt that we’ll be overstaffed any time soon. Until then we’ll just have to pick our battles and avoid spreading the already scarce resources too thin (hence the seemingly endless postponing of cross platform builds). So as always, help is welcome (i.e. to get those mac builds going).
Thanks for your comment. So far I’ve used it on Ubuntu, and I can’t wait for a Mac build.
Is the staffing issues due to budget on Kolab’s side or finding the right candidate later soon? So hopefully, you’ll soon have an additional developer to join you this year you say, that would certainly help and allow for more time to do spot bugs and test the client further.
One additional feature that I find immeasurably useful on Kolab (elastic client) is Kolab tags. Is it foreseeable that this feature will be something which will make it into Kube (I don’t expect until much later on), but this feature in essence makes GMAIL useless to me, as it combines folders AND labels 🙂
Keep up the good work