[Tickets #1414] RESOLVED: Add original owner's categories and colors to calendars

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=1414
-----------------------------------------------------------------------
 Ticket             | 1414
 Updated By         | kevin_myer at iu13.org
 Summary            | Add original owner's categories and colors to calendars
 Queue              | Kronolith
 Version            | 2.0.2
 State              | Rejected
 Priority           | 1. Low
 Type               | Enhancement
 Owners             | 
-----------------------------------------------------------------------


kevin_myer at iu13.org (2005-02-19 06:07) wrote:

You've also intentionally made it impossible to determine whose event you're
looking at, without clicking on an event to see which calendar it's
associated with, or without toggling calendars on and off to see what makes
the event disappear.

Using a simple, but frustrating real-life example for me:

Two users share their calendars with each other.  Each calendar contains all
the meetings, and vacation days, etc.  for that user.  If they both use the
same Category name, each user sees all events as "theirs" - i.e. they show
with their colors.  Let's say we both use a Business category.  Mine is red
and my staff member's is green.  There's no way to visually communicate that
my vacation day is mine and that my staff member's vacation day is theirs. 
Because both vacation days show up as the same color (red) on my calendar,
based on my category color choices.  Likewise on my staff member's calendar,
they're both green.  Throw in a few more staff members and misery starts to
mount, to the point that Kronolith no longer becomes a viable shared
calendaring solution.  With my patch, my vacation day is red, and my staff
member's vacation day is green.

There needs to be a visible way of communicating whose event I'm looking at.
 Unless I'm missing something, this does not currently seem possible and
since my idea is apparently not correct, I'm open to any additional ways of
having event ownership be easily visible.

Maybe a screenshot of the current state of affairs and my patched state of
affairs would help clarify why this is a problem and how I've solved it for
myself?