From 1fb523c0fa814389a944091e5c03e38b24634191 Mon Sep 17 00:00:00 2001
From: Andrew McMillan Novell Evolution is available in most Linux distributions. The CalDAV support was supposedly written
-in a frenzy of hacking one day when the draft specification was at around revision 8. As a result there
-was little in the way of a repository available to test against until recently. 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
-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: Hopefully those will be fixed before too long... The Mozilla calendar project offers their calendar under two different names: Sunbird is a standalone calendar
-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. 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. It is early days yet for the Mozilla calendar in it's current incarnation so no doubt there are other quirks
-with Mozilla's handling of CalDAV too, so perhaps take a look at their bugzilla. As at version 0.3, you should be aware of this bug with empty CalDAV calendars which can be
-confusing. Add your calendar, create an event and then re-start the program before saying that things
-are not working! Mulberry is the most well-behaved of the applications I have been able to use. It does have some
-bugs, however, and a particular annoyance around it's use of non-standard names for time zones. Mulberry
-is the only client I have used so far which can issue a MKCALENDAR command or which will display a
-hierarchy of calendars from one configured URL. Unfortunately Mulberry is not 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 thought that RSCDS had regressed
-somewhat and that these instructions didn't exactly work... :-) It turned out that these instructions worked just fine when I followed
-them to the letter the next day. Go figure. I think I need to record some screenshots of this one... If you intend to have users accessing the Really Simple CalDAV Store with more than one client
-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 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: 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 Evolution
-
-
-Sunbird / Lightning (Mozilla Calendar)
-
-
-Mulberry
-
-
+ case 'icon': $icons[$matches[1]] = $file; break;
+ case 'screenshot': $screenshots[$matches[1]] = $file; break;
-Cross-client Interoperability Considerations
-
-
-/caldav.php/ and anything following that is the calendar namespace.
-caldav://calendar.example.net/caldav.php/username/home/
-
-collection records when Evolution, Lightning
-or Sunbird attempt to store to a non-existent collection.
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:
+
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 +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 RSCDS is not yet perfect but basic operation is satisfactory. I will be +concentrating on making RSCDS interoperate with Chandler over coming releases.
diff --git a/docs/website/clients/Chandler-dialog1.png b/docs/website/clients/Chandler-dialog1.png new file mode 100644 index 0000000000000000000000000000000000000000..c9b817785f127507091095aec8f732e9f02d1a19 GIT binary patch literal 4285 zcmZu!c{mha_a9NV#xCpFmk7leYGiE;QZZR)Xe4GZWhtUavTq?@LiQz0W5!q-S<)u5 zgk+GBr6ywR%UFhZec$iRAW24GEgiW4}wOD ZD^_mxD(%vd4!cmP2*L?SlKkietB=m
zao8m zwI%|02zGRUpn= o;&gey-Onlws)912VU)eE*5#GH?q6Ws;Gdb
z`e61{3~f2UK#YNq*OG<4TWl2*pP&{gMcr3*kp#)toDe`ocH{Ry-%ol}qk4~BV~A9G
zy=d^ADPpS8|CtDxDA3G}gKPporJ_i?5}8^iV@)>r#$C55H`mHmnW`gs*^-t&j-4GY
z>*-xL3slsI-~&)(3z3bgzJFwNTIKbXm9EWVlV6hwgZTvW=$)Nz+gumj01-K)F=0&6
ztPHPIgOy~EK|kdKM+nA&yi}z1^pQ&EGJ}>LuSW!3QeTXRN`|^|Gw3K{XU7s`tu(jv
zh!(ed#Z|613DHz{J#0EsO6Su}+RVXGV*&WEkNJ#^ }0IFfQk@jGPUz-
zb@dyS2s^^kn6p1i9)uJ`P#Hg|ro>wW*=P+c-lGcaK*bsb0VoHMl=SU@m`#8uVE8b*
zG#j4v{kL5IhsgeykzZ1_OG*rw@L%ocKg`%>_p<%?KjtG2vu+Cg4s=Zv1ZY}2om}I`
z4PPwO+Sl6rC8tDqR3e7KB%-+cP=#RA(0=xGtBHHh% Evolution is available in most Linux distributions. The CalDAV support was supposedly written
+in a frenzy of hacking one day when the draft specification was at around revision 8. As a result there
+was little in the way of a repository available to test against until recently. 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
+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: There may also be bugs in Evolution's handling of SSL with CalDAV - I couldn't get it to work reliably. Hopefully those will be fixed before too long... ~P1pet+6Pbt@VO
zqbKta&7TNhH@$YPs<%FHl8MuITn)$qvv}u};FON43a-63UrinrvYgv-Kj+QapY84$
z>z$-KR3E7!sd NSrY@x0NYj%#J7qrfqe_6
z{JL9*a|`&8SxEMHxWb){ldFrVgNO`QV;FT(>c6?e20;^Kqb2WR%>IGCNlD1VH659y-QE6=mwJiDb?UC)Cf+4|mNR50
zw-nM?x?m+HTOJU98q~S&B=?$|P5Ms*mB`TWh9nNz4N*Gm?N0az#ZA2ZKz4dwnZnw6
zp0}a6Hxe>x^;=73&dNFBEIj(zj%b(A?n!y`$P*Ekap5l2zX!vMd*{Pta-GR#3^Qh2
zb|KFsn$n)dp9ysyaipo*wA)dOH>T~#X%e#!gR#yKkz(GJjoUjA+C;|#BJe>=cSsY5
zS&m6}MfbRqim2_-_J74UU8RCX
z2Vy*pIKLZ}7jb(&2KB8;;<~`QCC|>B{-A`E)LEpkiPtCV1A3qRG1br#A=a$|KWg}0
zKGbGfFuhB+D0;tTwwaf|XUP;{>lU)e^n6fSku!-#iWc)EV3Vi)NQlbhI{PgDou%ds
zVhDy0wd~DiGYmQ!kvrd^RzWMIdM}erZ$SDxdz#Pv#yFgXkuM7L4g%S`zKkMYRrJNm
zVYA;2FMW}FN5wJ;nvwlJ`c}-X*zTA9jT_#Oes8(j5Fb98pRJ08*4JU0p5JNtuw<1W
z0tG%W?nv(2yK-t&e-HIMIk=hC@rJ=~cI6}y!%`dONEX=w+rdc+PhK7mmCv3VeG9up
zzNEv8ZSgELETz}0`PEG+&-)+CIo^2OkvbWxyFhu%KxjHXh>RVCWJ1`(PbJv)-|&W1
z{_gA&452|h{0aA!!-{~TzVtpno{J)0=b1FVIAs7me~>TFUBzqLyZ$H2i;6_dgL+&q
zAS1Q0U6GFi^xQkb1k2Mk?!w{z1|6@t
Yrp#UnA-b2r2>rMthE$|MWTc!+pCuO`HRhapgHUo}G`i26Kn+
z-7j9ha}#Mr{gD$ZzU$^1S9<^5_m(O3Npe*nT48mGQR$arql`YN(jfhhq%CuO&>@U}Y_Ey3}7
z9V6)-B7HcbhRt|A_2@?*%cUzH{OUDIkT@v6`B|we7!Tt!cmwCfW6M%KtQX&
+
+caldav://server.domain.name/caldav.php/username/home/, enter your user name for RSCDS and click "OK".
SrQJ
zhWiJj2?~6Ersmtpthr6;dTr2)7jSa5U`As(5vUs5h2&9xRqSU{4IjDQ_r4;V_x?W{
zT?VX(R!N`8S^yJ4id`9wclkqxqz`_@g~a(`$#w+%j72Q;)qE)6A^N$KeaQ$4