The proposition of the Kube campaign is the following:
You sign-up now via Kube for a Kolab Now account, and pay only for the currently available feature-set that Kube provides at the moment. The web client will be limited to the same feature-set, but as Kube progresses and covers more features you will also get those features for the web client, while you get to keep your reduced subscription price.
It was already previously possible to navigate through Kube by moving the keyboard focus using tab and arrow keys, however that is neither fast nor efficient. To be able to really blaze through your Inbox we naturally require VIM style keybindings. To move through the UI we want to be able to go through folders, threads and mails using a single key press, without worrying where the focus currently is.
Around FOSDEM this year we have found some fresh manpower for Kube! Please welcome Rémi, who is doing an internship with us, and is working on Kube during that time. He was quick to land his first few patches and is now busy implementing the first few steps for CalDAV based calendaring support.
I for one am exited to see what he will come up with =)
The most recent addition to Kube is fulltext search. It’s a complex enough topic that we don’t really want to implement it in our key-value store that we use for the rest of the data, which is why we’re using Xapian to do the heavy lifting.
Kube is an offline capable client, and as such we also want search to work without an internet connection. However, we naturally can only search the data that you have available locally. Normally this means we’ll have subject and recipients indexed for all your mail, and the complete content for all mails that you have every viewed/downloaded.
In the long run we’ll want to extend that with server-side searching for when you’re connected to the server, so that you could indeed search through all your data, without having to first download it all. But that is a task for another day.
So here it goes; Fast as you type searching of your emails:
For more info about Kube, please head over to About Kube.
To build a reliable product it is essential that we build ways for us to ensure that what we build also works as expected. In its simplest form that means that you try what you build, the assumption being that if it works for you, it works for everyone.
By now we all know that “works for me” is not enough, but there are also a variety of additional challenges;
It’s not enough to only test when a feature is first implemented, the tests need to be repeated regularly to ensure nothing breaks that once worked.
There is a balance to be struck between over- and under- testing. Tests need to be of high quality and have to be maintained with the system, otherwise they become a burden instead of an asset.
The right things need to be tested. Test things that are too trivial and you end up with loads of tests with little value (but a maintenance cost). Test things that are too complex and your tests become fragile and don’t tell you what broke, making fixing it harder.
The testenvironment needs to be realistic enough so we test the right things (e.g. we don’t want to test the internet connection typically), yet also removes the bits that we don’t have under our control, so we test our system only. That ensure that the test remain reliable and are fast to run (so they are run regularly).
Secure and confidential communication is an important requirement for a society, and something, I think, we should provide to as many people as possible. A popular mechanism to achieve this is to use public-key cryptography, which allows a person to encrypt a message to a persons key, so that only the intended recipient can decrypt the message. This means that even if an attacker would get his hands on the encrypted message, without the key, it’s only useless gibberish.
As one of the primary usecases of Kube is communication, it should also support you in doing so in a secure and confidential fashion.
One of the most frustrating user experiences is when you get an error message that you can’t do anything about, or even worse, that you don’t even understand.
While it’s very well possible that the error message is entirely justified, wouldn’t it be great if the system didn’t just tell you that something is wrong, but also what you can do about it? Error messages can be even more infuriating if they block you from doing your work even if they are not directly related, thus interrupting your workflow unnecessarily. Wouldn’t you rather have a notification that something does not work as it should, while otherwise letting you go about what you wanted to do, instead of just popping up a blocking popup that you have to click away before you can do anything else?