Comment 3 for bug 1417158

This would be a HUGE quality of life improvement. But having written a blocking system for a calendar myself (buisiness, so I'm sadly not allowed to duplicate this work in FOSS) I know it's a bit tricky to:
- calculate the overlapping (to be able to have non-overlapping events on the same row/column)
- calculate the position in the stack for all blocks on the same overlap (to stack overlapping events in their column/row)
- check constraints and limits (like "max 3 multi-day-events")
- apply vertical or horizontal layout

But no rocket science at all. I wish I could help more. Darn...

One hint: I found that, if you do the above correctly and store very few state and position informations in event objects, you can use the same logic for basically any layout that requires you to display blocks of events (day, week, all-day, multi-day, multiple-all-day, ...). Just in one case you (whoever will take a look at this) need to look at the time and in the other case you only need the date.