summaryrefslogtreecommitdiffabout
path: root/bin
authorzautrix <zautrix>2004-10-26 16:53:49 (UTC)
committer zautrix <zautrix>2004-10-26 16:53:49 (UTC)
commit8fd100b2186e83838223f798c45637721b7b1fe3 (patch) (side-by-side diff)
tree096fde05be4d8f611a9b5accbf580764630c2712 /bin
parentb20ce8d246ff4662bd33dccfc98a75aece6705b1 (diff)
downloadkdepimpi-8fd100b2186e83838223f798c45637721b7b1fe3.zip
kdepimpi-8fd100b2186e83838223f798c45637721b7b1fe3.tar.gz
kdepimpi-8fd100b2186e83838223f798c45637721b7b1fe3.tar.bz2
chaged sync howto
Diffstat (limited to 'bin') (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
@@ -24,6 +24,7 @@ sync KA/Pi+KO/Pi running on Windows with KDE via network.
The setup+sync procedure is:
+0) How the syncing works
1) Installing KA/Pi+KO/Pi on the Z
2) Installing desktop version of KA/Pi+KO/Pi on the desktop
3) Connection your Z to the desktop via network
@@ -32,6 +33,47 @@ The setup+sync procedure is:
5) Enable remote sync in KA/Pi+KO/Pi on the desktop
6) Sync
+*****************************************************
+0) How the syncing works
+*****************************************************
+
+After setting up everything, the following actions will
+be performed when syncing:
+User enables "remote pi-sync" on desktop.
+User chooses "sync with configured desktop profile" on the Z.
+Z sends sync request via network to configured IP/port/password.
+KO/Pi on desktop detects sync request and syncs with KDE (configurable!).
+A window pops up, that KO/Pi on desktop is in "remote syncing mode".
+If a conflict occurs when syncing KO/PI<->KDE on the desktop,
+automatically the newest entry is choosen.
+(To avoid the need of user interaction)
+KO/Pi on desktop sends synced file to Zaurus.
+KO/Pi on desktop is in "waiting mode" to get synced file back.
+Zaurus is syncing it's own calendar with the received file.
+Here can be some user interaction needed, i.e.
+if the sync profile is configured as
+"ask for every entry on conflict" and a conflict occurs.
+Zaurus sends back synced file to desktop.
+Syncing on Zaurus is complete now.
+KO/Pi on desktop gets back synced file.
+KO/Pi on desktop removes all entries in its own calendar and
+reloads the synced file.
+KO/Pi on desktop syncs with KDE.
+After syncing with KDE is finished, KO/Pi closes
+the "remote syncing mode" window and displays
+a "syncing complete" message in the headline.
+
+The actual syncing KO/Pi on desktop <-> KDE is
+performed by a small command line tool "kdecaldump",
+which writes/reads the complete KDE calendar resources to
+a file/from a file.
+KO/Pi tags changed entries such that an unchanged entry
+is not changed in KDE by kdecaldump. That is important for
+calendar entries in KDE, stored in a "disconnected IMAP" calendar resource.
+
+
+Same way is KA/Pi working.
+
*****************************************************
1) Installing KA/Pi+KO/Pi on the Z
@@ -223,6 +265,7 @@ the following, if you want to sync your Zaurus with KDE:
(It syncs will all resources in KDE, that are not "readonly").
Start KO/Pi on the desktop.
+If Kontact or KOrganizer is running, save the calendar!
Connect the Z with the USB cable to your desktop.
(Or to the local network).
Choose on the Z the menu:
@@ -243,7 +286,7 @@ xx is greater or equal to the number of todos.
That behaviour is caused by a bug in KDE.
(In KDE, everytime a subtodo is loaded,
it's "last modified" settings are set to the current time - ouch!)
-I hope that bug will be fixed soon.
+I hope I can fix this bug in KDE soon.