Re: [evolution-patches] patch for bug #62857 [calendar]
- From: Rodrigo Moya <rodrigo novell com>
- To: P Chenthill <pchenthill novell com>
- Cc: evolution-patches ximian com
- Subject: Re: [evolution-patches] patch for bug #62857 [calendar]
- Date: Fri, 20 Aug 2004 16:16:53 +0200
On Fri, 2004-08-20 at 06:19 -0600, P Chenthill wrote:
> Hi,
> Have attached the patch which makes all the components in
> recurrences availble
> in the view as soon as it is created.
>
looks ok, although we continue to have the recurrences problem we talk
about on IRC.
For those who don't know: GW stores each individual recurrence as an
individual appointment, so the GW backend in e-d-s does the same. This
gives us a lot of problems though: for instance, if a user creates an
event that recurs in the next 10 years every day, the GW server will
create 3650 appointments.
But that's not the worst: since each individual ECalComponent created
for each individual instance does not have a recurrence-id nor any
recurrence-related data, evolution treats them as normal events (with no
recurrences). Thus, the popup menu for the selected event does not show
up any of the recurrence-related items. That means that if the user
above changes her mind and wants to modify or remove the recurring event
she just created, she will have to go over the 3650 recurrences and
modify/remove them individually.
Might look like I am exaggerating :), but having recurring events recur
for ever is quite normal (at least for me). So, what does the GW server
do when the recurrence is 'for ever'?
So, the patch looks ok, please commit, but we need to deal with these
things.
--
Rodrigo Moya <rodrigo novell com>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]