Elastic: Kolab Notes

Last few weeks I was working on porting Kolab Notes plugin to Elastic. I wanted to see how it goes with some more serious chunk of our code base before I put my hands on Calendar, Tasks or Files. It was reasonably smooth, see the result…

Continue reading


Elastic: Kolab Tags

As I announced I’m working on porting Kolab plugins to Elastic. I just finished working on Kolab Tags functionality. In comparison to the old design we have two small changes:

– tags list is displayed below the folders list as before, but visually it is the same element. It is also not a tag-cloud, but a simple list. The tag-list related actions were put into the Actions menu in the list footer.

– we display tag color by applying the color to the tag icon.


We use tags functionality in other plugins, e.g. Tasks and Notes, however all of them use its own tags UI implementation. When working on these I’m going to unify and make them use the same tag-list look/behavior.

Elastic: Core functionality covered

Still in a need of a graphic designer! I’m finishing work on core functionality for the new Roundcube theme. Almost all of the current functionality as of now is implemented in Elastic, including core plugins. In this post I’m providing information about some recent updates (with some sreenshots).

Continue reading

Event start date not in the recurrence pattern?

It came from Outlook users but we’ve found out it’s indeed a real issue. For example assume it is Thursday and you create a new event that is recurring weekly on Fridays. Did you ever wanted such an event to occur on the day it has been created? I think if you want Fridays that’s Fridays only. Of course you could add an exception later, so the event is moved to another day for a specific occurrence, but that’s another story.

Now if you create such an event, first occurrence will be on this Thursday and Friday. I believe in most cases this is not an intended behavior. It also creates confusion if you use more than one client and they handle this case differently. You will see a difference in displaying your calendar across clients.

This is how Kolab works and for example Thunderbird Lightning too, but not Outlook. In Kolab we’ll solve this by additional checkbox and will default to Outlook behavior. If checked, the start date of the event will be aligned with the first occurrence of the event (on or after the original creation date).


Improvement in (free-busy) availability finder

When planning a meeting with other people in your organization you use Availability Finder widget. It’s granularity from the beginning was one hour, no less no more. On the other hand in Calendar view you could configure that granularity, i.e. number of slots in an hour.

My changeset that awaits a review will fix this inconsistence. As you see on the picture below the same granularity will be used both in calendar view and availability finder.

Without my fix the whole slot is busy/tentative no matter how long the existing events of the user would take. In this case the user is free from 08:00 to 08:30 and busy from 08:30 to 09:00. With my fix the whole one hour slot will be split into “sub-slots”, so you can plan the new event easier and with more precise timing.


This change also fixes issues of the selection box (the dark rectangle at 06:30-07:00 above). Its moves on Previous/Next Slot action were a little bit unexpected sometimes. Now it’s more precise and uses the same granularity.