[#4760] Better represent that multi-day events are the same event
Summary Better represent that multi-day events are the same event
Queue Kronolith
Queue Version HEAD
Type Enhancement
State Accepted
Priority 1. Low
Owners
Requester cbs@cts.ucla.edu
Created 2006-12-11 (5067 days ago)
Due
Updated 2008-11-09 (4368 days ago)
Assigned
Resolved
Milestone
Patch No

Comments
cbs@cts.ucla.edu 2006-12-11 13:21:31
all-day appointments that last several days do not show up as 
contiguous blocks in the week and work-week views.  This is especially 
confusing if there are multiple appointments that partially overlap.



I've started reworking the week/work-week view so that all-day 
appointments are displayed as a single contiguous block.  I'm 
attaching a screen capture showing the changes to this.  I'll attach 
patches for lib/WeekView.php, lib/DayView.php, 
templates/day/all_day.inc, and themes/screen.css

cbs@cts.ucla.edu 2006-12-11 13:22:10
patch for lib/WeekView.php

cbs@cts.ucla.edu 2006-12-11 13:23:02
patch for lib/DayView.php

cbs@cts.ucla.edu 2006-12-11 13:24:01
patch for all_day.inc

cbs@cts.ucla.edu 2006-12-11 13:27:02
patch for screen.css



I have several other changres to the css, so the line numbers might be 
off.  The changes are minor, and should be easy to eyeball (changing 
.*-eventbox -mox-border-radius from 15px to 5px, and adding classes 
for .blankline and .skip)

Chuck Hagenbuch <chuck@horde.org> 2006-12-11 16:04:38
That looks great and I'm sure will be appreciated. Unfortunately I 
need to ask you to do these patches against HEAD, not the stable 
version. This is our policy for all enhancements; they go into HEAD 
and then are merged to the stable versions when appropriate. If the 
differences aren't great we'll try to use the same patches, but in 
this case Kronolith has been reorganized enough that this really needs 
to be done in HEAD.



Thanks!

cbs@cts.ucla.edu 2006-12-11 17:16:22
I won't be able to get to any forwarding porting until mid-January at 
the earliest.  I'm doing a stable deployment at the end of December, 
and all of my "feature" work will be based on that.



In the meantime, do you want updates to the prior patchset attached to 
this bug, or would you prefer that I hold everything locally until I 
have time to patch head?

Chuck Hagenbuch <chuck@horde.org> 2006-12-11 22:48:20
> I won't be able to get to any forwarding porting until mid-January at

> the earliest.  I'm doing a stable deployment at the end of December,

> and all of my "feature" work will be based on that.



I can understand that; I hope you understand that from our 
perspective, for stability, changes really need to go into HEAD first 
so that what gets merged down to the stable releases is, well, stable.



> In the meantime, do you want updates to the prior patchset attached

> to this bug, or would you prefer that I hold everything locally until

> I have time to patch head?



I'd prefer you held it until you had a HEAD patch. I'm going to stall 
this ticket for now, but I do hope you have time to get back to it 
later.



Thanks for your contributions,

-chuck

Chuck Hagenbuch <chuck@horde.org> 2008-11-09 02:30:52
We should have some visual and/or logical clue that multi-day events

are the same event. Especially they shouldn't have two separate delete

buttons that look as though they delete different things.

From #7485:



Complicated ideas include having the event bubbles connect across days.



A simple idea that might eliminate the worst confusion would be to not

show delete or edit buttons the 2nd, 3rd, + times an event is shown in

the same view.



This would NOT apply to recurring events, since there are already

sensible different actions for delete and edit based on which

recurrence is clicked.