From 1efa5342867472a31ec571dc90c441df44778147 Mon Sep 17 00:00:00 2001 From: Andrew McMillan Date: Thu, 30 Dec 2010 12:28:07 +1300 Subject: [PATCH] Updated information about Chandler. Signed-off-by: Andrew McMillan --- docs/website/clients/Chandler-details.php | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/docs/website/clients/Chandler-details.php b/docs/website/clients/Chandler-details.php index 9f395937..ba301955 100644 --- a/docs/website/clients/Chandler-details.php +++ b/docs/website/clients/Chandler-details.php @@ -13,15 +13,11 @@ written in Python.

Caveats

-

At version 0.7alpha3 the calendar is subscribed and displayed, but the 'displayname' property -which the server sends is not used and the calendar is displayed with a blank name. Double-click -on your new calendar and enter a name in the space available.

-

Chandler describes itself as 'an experimentally usable calendar', and it certainly feels that way. It also will only synchronise to the CalDAV server either when you press the "Sync" -button or with a default frequency of hourly. This is quite different to the other clients I +button or with a default frequency of quarter-hourly. This is quite different to the other clients I have used which all aggressively push new and changed items to the server as soon as possible, but which may be lazy about fetching updates.

-

Operation with DAViCal is not yet perfect but basic operation is satisfactory. I will be -concentrating on making DAViCal interoperate with Chandler over coming releases.

+

Operation with DAViCal seems generally fine although Chandler does not correctly display the account +information correctly, even if it seems to remember it internally.