summaryrefslogtreecommitdiffabout
Unidiff
Diffstat (more/less context) (ignore whitespace changes)
-rw-r--r--bin/kdepim/Zaurus-KDE_syncHowTo.txt45
1 files changed, 44 insertions, 1 deletions
diff --git a/bin/kdepim/Zaurus-KDE_syncHowTo.txt b/bin/kdepim/Zaurus-KDE_syncHowTo.txt
index 90c6237..5aad5da 100644
--- a/bin/kdepim/Zaurus-KDE_syncHowTo.txt
+++ b/bin/kdepim/Zaurus-KDE_syncHowTo.txt
@@ -25,4 +25,5 @@ sync KA/Pi+KO/Pi running on Windows with KDE via network.
25The setup+sync procedure is: 25The setup+sync procedure is:
26 26
270) How the syncing works
271) Installing KA/Pi+KO/Pi on the Z 281) Installing KA/Pi+KO/Pi on the Z
282) Installing desktop version of KA/Pi+KO/Pi on the desktop 292) Installing desktop version of KA/Pi+KO/Pi on the desktop
@@ -33,4 +34,45 @@ The setup+sync procedure is:
336) Sync 346) Sync
34 35
36*****************************************************
370) How the syncing works
38*****************************************************
39
40After setting up everything, the following actions will
41be performed when syncing:
42User enables "remote pi-sync" on desktop.
43User chooses "sync with configured desktop profile" on the Z.
44Z sends sync request via network to configured IP/port/password.
45KO/Pi on desktop detects sync request and syncs with KDE (configurable!).
46A window pops up, that KO/Pi on desktop is in "remote syncing mode".
47If a conflict occurs when syncing KO/PI<->KDE on the desktop,
48automatically the newest entry is choosen.
49(To avoid the need of user interaction)
50KO/Pi on desktop sends synced file to Zaurus.
51KO/Pi on desktop is in "waiting mode" to get synced file back.
52Zaurus is syncing it's own calendar with the received file.
53Here can be some user interaction needed, i.e.
54if the sync profile is configured as
55"ask for every entry on conflict" and a conflict occurs.
56Zaurus sends back synced file to desktop.
57Syncing on Zaurus is complete now.
58KO/Pi on desktop gets back synced file.
59KO/Pi on desktop removes all entries in its own calendar and
60reloads the synced file.
61KO/Pi on desktop syncs with KDE.
62After syncing with KDE is finished, KO/Pi closes
63the "remote syncing mode" window and displays
64a "syncing complete" message in the headline.
65
66The actual syncing KO/Pi on desktop <-> KDE is
67performed by a small command line tool "kdecaldump",
68which writes/reads the complete KDE calendar resources to
69a file/from a file.
70KO/Pi tags changed entries such that an unchanged entry
71is not changed in KDE by kdecaldump. That is important for
72calendar entries in KDE, stored in a "disconnected IMAP" calendar resource.
73
74
75Same way is KA/Pi working.
76
35 77
36***************************************************** 78*****************************************************
@@ -224,4 +266,5 @@ the following, if you want to sync your Zaurus with KDE:
224 266
225Start KO/Pi on the desktop. 267Start KO/Pi on the desktop.
268If Kontact or KOrganizer is running, save the calendar!
226Connect the Z with the USB cable to your desktop. 269Connect the Z with the USB cable to your desktop.
227(Or to the local network). 270(Or to the local network).
@@ -244,5 +287,5 @@ That behaviour is caused by a bug in KDE.
244(In KDE, everytime a subtodo is loaded, 287(In KDE, everytime a subtodo is loaded,
245it's "last modified" settings are set to the current time - ouch!) 288it's "last modified" settings are set to the current time - ouch!)
246I hope that bug will be fixed soon. 289I hope I can fix this bug in KDE soon.
247 290
248 291