author | zautrix <zautrix> | 2004-10-26 16:53:49 (UTC) |
---|---|---|
committer | zautrix <zautrix> | 2004-10-26 16:53:49 (UTC) |
commit | 8fd100b2186e83838223f798c45637721b7b1fe3 (patch) (unidiff) | |
tree | 096fde05be4d8f611a9b5accbf580764630c2712 | |
parent | b20ce8d246ff4662bd33dccfc98a75aece6705b1 (diff) | |
download | kdepimpi-8fd100b2186e83838223f798c45637721b7b1fe3.zip kdepimpi-8fd100b2186e83838223f798c45637721b7b1fe3.tar.gz kdepimpi-8fd100b2186e83838223f798c45637721b7b1fe3.tar.bz2 |
chaged sync howto
-rw-r--r-- | bin/kdepim/Zaurus-KDE_syncHowTo.txt | 45 |
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 | |||
@@ -26,2 +26,3 @@ The setup+sync procedure is: | |||
26 | 26 | ||
27 | 0) How the syncing works | ||
27 | 1) Installing KA/Pi+KO/Pi on the Z | 28 | 1) Installing KA/Pi+KO/Pi on the Z |
@@ -34,2 +35,43 @@ The setup+sync procedure is: | |||
34 | 35 | ||
36 | ***************************************************** | ||
37 | 0) How the syncing works | ||
38 | ***************************************************** | ||
39 | |||
40 | After setting up everything, the following actions will | ||
41 | be performed when syncing: | ||
42 | User enables "remote pi-sync" on desktop. | ||
43 | User chooses "sync with configured desktop profile" on the Z. | ||
44 | Z sends sync request via network to configured IP/port/password. | ||
45 | KO/Pi on desktop detects sync request and syncs with KDE (configurable!). | ||
46 | A window pops up, that KO/Pi on desktop is in "remote syncing mode". | ||
47 | If a conflict occurs when syncing KO/PI<->KDE on the desktop, | ||
48 | automatically the newest entry is choosen. | ||
49 | (To avoid the need of user interaction) | ||
50 | KO/Pi on desktop sends synced file to Zaurus. | ||
51 | KO/Pi on desktop is in "waiting mode" to get synced file back. | ||
52 | Zaurus is syncing it's own calendar with the received file. | ||
53 | Here can be some user interaction needed, i.e. | ||
54 | if the sync profile is configured as | ||
55 | "ask for every entry on conflict" and a conflict occurs. | ||
56 | Zaurus sends back synced file to desktop. | ||
57 | Syncing on Zaurus is complete now. | ||
58 | KO/Pi on desktop gets back synced file. | ||
59 | KO/Pi on desktop removes all entries in its own calendar and | ||
60 | reloads the synced file. | ||
61 | KO/Pi on desktop syncs with KDE. | ||
62 | After syncing with KDE is finished, KO/Pi closes | ||
63 | the "remote syncing mode" window and displays | ||
64 | a "syncing complete" message in the headline. | ||
65 | |||
66 | The actual syncing KO/Pi on desktop <-> KDE is | ||
67 | performed by a small command line tool "kdecaldump", | ||
68 | which writes/reads the complete KDE calendar resources to | ||
69 | a file/from a file. | ||
70 | KO/Pi tags changed entries such that an unchanged entry | ||
71 | is not changed in KDE by kdecaldump. That is important for | ||
72 | calendar entries in KDE, stored in a "disconnected IMAP" calendar resource. | ||
73 | |||
74 | |||
75 | Same way is KA/Pi working. | ||
76 | |||
35 | 77 | ||
@@ -225,2 +267,3 @@ the following, if you want to sync your Zaurus with KDE: | |||
225 | Start KO/Pi on the desktop. | 267 | Start KO/Pi on the desktop. |
268 | If Kontact or KOrganizer is running, save the calendar! | ||
226 | Connect the Z with the USB cable to your desktop. | 269 | Connect the Z with the USB cable to your desktop. |
@@ -245,3 +288,3 @@ That behaviour is caused by a bug in KDE. | |||
245 | it's "last modified" settings are set to the current time - ouch!) | 288 | it's "last modified" settings are set to the current time - ouch!) |
246 | I hope that bug will be fixed soon. | 289 | I hope I can fix this bug in KDE soon. |
247 | 290 | ||