diff --git a/docs/website/clients/Chandler-details.php b/docs/website/clients/Chandler-details.php index 9f2913dc..8d6a21d4 100644 --- a/docs/website/clients/Chandler-details.php +++ b/docs/website/clients/Chandler-details.php @@ -2,14 +2,17 @@

The Open Source Applications Foundation are developing Cosmo, which is a CalDAV server written in Java and Chandler, which is a CalDAV capable mail and calendaring application written in Python.

+

Basic setup is as follows:

+
  1. Select "Subscribe" from the "Collection" menu.
  2. Enter a URL like: "http://calendar.example.net/caldav.php/username/home/" (click "Subscribe")
     
  3. You will then be prompted for a username/password with in an expanded dialog. Enter these and click "Subscribe" again.
     
  4. You should now have a new calendar showing.
-

Caveats

+ +

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.

diff --git a/docs/website/clients/Evolution-details.php b/docs/website/clients/Evolution-details.php index 992d3412..9381a94f 100644 --- a/docs/website/clients/Evolution-details.php +++ b/docs/website/clients/Evolution-details.php @@ -8,10 +8,12 @@ was little in the way of a repository available to test against until recently.<
  • Choose a type of "CalDAV", enter a name, and a URL such as caldav://server.domain.name/caldav.php/username/home/, enter your user name for RSCDS and click "OK".
     
  • You should now be prompted for a password for that username. Enter the password and your calendar should now show.
    • + +

    Caveats

    If you have problems with Evolution, you will need to quit evolution, remove the cache file which will be in ~/.evolution/cache/calendar/ and restart. If you still have problems try doing that, but killing evolution-data-server in addition.

    -

    Sometimes evolution writes error messages into the cache file, so if you have ongoing problems you may want to +

    Sometimes Evolution writes error messages into the cache file, so if you have ongoing problems you may want to take a look inside that.

    There are some quirks with Evolution's handling of CalDAV too, so perhaps take a look at the following bugs:

    diff --git a/docs/website/clients/Evolution-dialog1.png b/docs/website/clients/Evolution-dialog1.png index 66be50a0..7e678bad 100644 Binary files a/docs/website/clients/Evolution-dialog1.png and b/docs/website/clients/Evolution-dialog1.png differ diff --git a/docs/website/clients/Interoperability-details.php b/docs/website/clients/Interoperability-details.php index 45084b95..96c9834a 100644 --- a/docs/website/clients/Interoperability-details.php +++ b/docs/website/clients/Interoperability-details.php @@ -3,17 +3,19 @@ then you should attempt to structure the URLs which they use to access the system in the way that Mulberry does it.

    Basically, Mulberry breaks the URL into three parts:

    + +

    The host name is, of course, up to you. The 'root path' should be /caldav.php/ and anything following that is the calendar namespace.

    Within the calendar namespace RSCDS uses the first element of the path as the user or resource name, so that a client connecting at the root path can see all of the (accessible) users and resources available to them (Mulberry displays this hierarchy) with any calendars below that.

    Effectively this means that in Evolution, Sunbird and Lightning you should really specify a calendar URL which is something like:

    -caldav://calendar.example.net/caldav.php/username/home/
+http://calendar.example.net/caldav.php/username/home/

    Then, when more calendar client software sees it as useful to be able to browse that hierarchy, you won't be up for any heavy database manipulation.

    I may well enforce this standard in some way before release 1.0, as well as auto-creating the collection records when Evolution, Lightning diff --git a/docs/website/clients/Mozilla-details.php b/docs/website/clients/Mozilla-details.php index 1280f287..a3c35da0 100644 --- a/docs/website/clients/Mozilla-details.php +++ b/docs/website/clients/Mozilla-details.php @@ -4,6 +4,7 @@ application, and Lightning is a Thunderbird extension. The two are essentially the same, as far as RSCDS is concerned, and these instructions should work for either of them.

    +
    1. Select "New Calendar" from the "File" menu.
    2. Choose "On the Network" (click "Next")
       
      3. @@ -11,6 +12,7 @@
    3. Give the calendar an appropriate display name, and choose a colour for events on this calendar. (click "Next")
       
    4. click "Finish"
    +

    Caveats

    At version 0.3 the Mozilla calendar does not automatically refresh the calendar view, so if someone else has added a meeting you will have to manually refresh the view to see that.

    diff --git a/docs/website/clients/Mulberry-details.php b/docs/website/clients/Mulberry-details.php index 3da57e17..55a3a49e 100644 --- a/docs/website/clients/Mulberry-details.php +++ b/docs/website/clients/Mulberry-details.php @@ -19,7 +19,7 @@ PROPFIND requests.

  • Once you have a calendar created, you need to subscribe to it. One way is to right-click on it and choose 'Subscribe'.
    • -

    Caveats

    +

    Caveats

    Unfortunately Mulberry is not (yet) open-source, though it is free, so we must wait on the developer to fix the user interface niggles when he gets around to it.

    Note that Mulberry has a complex user interface. When I wrote this I went back into Mulberry and initially