Closed GoogleCodeExporter closed 8 years ago
I'm for adding ways to handle multiple calendars. It's there in Google cal and
in
Ical on MacOS X, TeamAgenda and probably in other calendar applications as well.
But it should not be limited to three calendars. If implemented it must be
possible
to have any amount of calendars, ways for the user to choose colors and names
for
each, choice to look an entire calendar to read only etc.
It's more to it than proposed above.
Original comment by jolle.carlestam
on 11 Aug 2009 at 9:45
There's actually a way to do what you're doing with the current codebase. The
eventRender option gives you access to both the calEvent data object and the
jquery
element that is used to render the calendar event. So you can just do this if
you want:
eventRender : function(calEvent, $event) {
$event.addClass(calEvent.calendarClass);
}
I'm not sure that i'd do it that way exactly myself but it demonstrates the
capability.
As far as multiple calendars go, you can already do this but it's up to you to
pull
the data from different places usign the data function option and combining the
results into a single object. From there give each event the appropriate style
and
meta-data to determine where it has come from for edits, drags, resizes etc.
I'm not convinced that this is something that should be built further into the
calendar itself but it sounds like we could certainly benefit from a
multi-calendar
demo to help people along. Thiings like the implementation of the calendar
switching,
ala ical, google calendar etc are quite likely things that different apps would
want
to do differently.
Everything i'm saying about the multi-calendar stuff is theoretical at the
moment - I
haven't actually implemented it yet but I can't see any reason why it can't be
done
quite simply. Especially with the recent option for different layouts for
overlapping
events.
I'll put a task in to put a demo for this together.
One final thing... for these types of posts, would you mind putting them in the
google group to start with as they really need discussion before they become an
enhancement. This way they're more discoverable for other people rather than in
this
case just being marked as 'won't fix'.
cheers,
rob
Original comment by robmo...@gmail.com
on 12 Aug 2009 at 7:42
Original issue reported on code.google.com by
ESTAN...@gmail.com
on 11 Aug 2009 at 6:15