[chandler-users] import from Google Calendar using ical

[Mimi Yin]

Hi Jeffrey,

Can Jason and others get around this problem for now by:

1. Subscribing to their Google Calendar with Chandler Desktop.
2. Exporting it from Chandler as an .ics file.
3. Deleting the Google Calendar subscriptiong from Chandler Desktop.
4. Re-importing their Google Calendar from the .ics file.

(If this works, I will write it up for the import/export FAQ page.)

Seems like the limitation here is that people can't get calendar data  
out of Google Cal as an independent (as in not bound by sharing  
access restrictions) .ics file.

That's separate from being able to subscribe to Google Calendars with  
Chandler Desktop and stay in sync, aka read-write sharing. If you  
want Chandler to stay in sync with your Google Calendar, allowing  
Chandler users to make local edits to read-only shares won't solve  
that problem.

Mimi

On Oct 9, 2007, at 11:14 AM, Jeffrey Harris wrote:

> Hi Jason,
>
>> It seems to have flagged many of my items as having pending changes.
>> Some of the items have one pending change and others have two pending
>> changes. e.g.
>>
>> 1. Subscriber changed the Location to
>
> This part is an easy-to-fix bug, is my guess.
>
>> 2. Subscriber changed the Rrule to FREQ=WEEKLY;BYDAY=TH;WKST=MO
>
> This is an unfortunate result of the fact that there isn't a canonical
> form for RFC2445 recurrence rules.  The BYDAY and WKST in that
> recurrence rule are redundant for most recurrence rules actual clients
> will let you create, so Chandler doesn't serialize them.
>
> This is unlikely to be an issue except when someone imports the same
> event from two different logical iCalendar sources, which I'm guessing
> is exactly what you did (although I imagine the iCalendar in question
> was probably identical, it came from two different sources from
> Chandler's perspective).
>
> We should probably translate RRULEs into a canonical form when we  
> import
> them from iCalendar to avoid this.
>
> I think in this case, you'd like to subscribe to a remote, read-only
> calendar but treat the items you receive as if they aren't read-only.
> Is that right?  Maybe that's a use case we should support.
>
> Sincerely,
> Jeffrey
>
> _______________________________________________
> chandler-users mailing list
> chandler-users at osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/chandler-users