| 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 (at) cts (dot) ucla (dot) edu |
| Created | 12/11/2006 (6729 days ago) |
| Due | |
| Updated | 11/09/2008 (6030 days ago) |
| Assigned | |
| Resolved | |
| Milestone | |
| Patch | No |
State ⇒ Accepted
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.
State ⇒ Stalled
the earliest. I'm doing a stable deployment at the end of December,
and all of my "feature" work will be based on that.
perspective, for stability, changes really need to go into HEAD first
so that what gets merged down to the stable releases is, well, stable.
to this bug, or would you prefer that I hold everything locally until
I have time to patch head?
this ticket for now, but I do hope you have time to get back to it
later.
Thanks for your contributions,
-chuck
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?
Version ⇒ HEAD
State ⇒ Feedback
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!
New Attachment: screen.css.diff
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)
New Attachment: all_day.inc.diff
New Attachment: DayView.php.diff
New Attachment: WeekView.php.diff
Priority ⇒ 1. Low
State ⇒ New
New Attachment: Picture 1.png
Queue ⇒ Kronolith
Summary ⇒ convert all-day appointments in week/work-week view so that multiple days are a contiguous block
Type ⇒ Enhancement
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