summaryrefslogtreecommitdiffabout
authorzautrix <zautrix>2004-10-26 16:53:49 (UTC)
committer zautrix <zautrix>2004-10-26 16:53:49 (UTC)
commit8fd100b2186e83838223f798c45637721b7b1fe3 (patch) (unidiff)
tree096fde05be4d8f611a9b5accbf580764630c2712
parentb20ce8d246ff4662bd33dccfc98a75aece6705b1 (diff)
downloadkdepimpi-8fd100b2186e83838223f798c45637721b7b1fe3.zip
kdepimpi-8fd100b2186e83838223f798c45637721b7b1fe3.tar.gz
kdepimpi-8fd100b2186e83838223f798c45637721b7b1fe3.tar.bz2
chaged sync howto
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
@@ -15,32 +15,74 @@ PIM data of the KDE.
15(addressbook and calendar data). 15(addressbook and calendar data).
16You need to install the desktop versions 16You need to install the desktop versions
17of KA/Pi+KO/Pi on the desktop. 17of KA/Pi+KO/Pi on the desktop.
18You need KDE version 3.3.0 or higher on your desktop. 18You need KDE version 3.3.0 or higher on your desktop.
19You need KA/Pi+KO/Pi version 1.9.11 or higher on the desktop 19You need KA/Pi+KO/Pi version 1.9.11 or higher on the desktop
20and on the Z. 20and on the Z.
21 21
22NOTE: Almost the same procedure will make it possible to 22NOTE: Almost the same procedure will make it possible to
23sync KA/Pi+KO/Pi running on Windows with KDE via network. 23sync KA/Pi+KO/Pi running on Windows with KDE via network.
24 24
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
293) Connection your Z to the desktop via network 303) Connection your Z to the desktop via network
30 (network connection can be set up via USB cable or (W)Lan 31 (network connection can be set up via USB cable or (W)Lan
314) Configuring KA/Pi+KO/Pi on Z for Sync 324) Configuring KA/Pi+KO/Pi on Z for Sync
325) Enable remote sync in KA/Pi+KO/Pi on the desktop 335) Enable remote sync in KA/Pi+KO/Pi on the desktop
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*****************************************************
371) Installing KA/Pi+KO/Pi on the Z 791) Installing KA/Pi+KO/Pi on the Z
38***************************************************** 80*****************************************************
39 81
40Download latest version of KA/Pi+KO/Pi from 82Download latest version of KA/Pi+KO/Pi from
41http://sourceforge.net/projects/kdepimpi/ 83http://sourceforge.net/projects/kdepimpi/
42Project KDE/Pim. 84Project KDE/Pim.
43Direct link is: 85Direct link is:
44http://sourceforge.net/project/showfiles.php?group_id=104103&package_id=112604 86http://sourceforge.net/project/showfiles.php?group_id=104103&package_id=112604
45Click on the version number to read the release notes/change log. 87Click on the version number to read the release notes/change log.
46Choose there the right precompiled package for your Z: 88Choose there the right precompiled package for your Z:
@@ -214,38 +256,39 @@ Configure / test KA/Pi on the desktop in the same way.
214Fill in the right value for the port (9198 in our examle) 256Fill in the right value for the port (9198 in our examle)
215in KA/Pi! 257in KA/Pi!
216 258
217***************************************************** 259*****************************************************
2186) Sync 2606) Sync
219***************************************************** 261*****************************************************
220 262
221After configuring everything as above, you have to do 263After configuring everything as above, you have to do
222the following, if you want to sync your Zaurus with KDE: 264the following, if you want to sync your Zaurus with KDE:
223(It syncs will all resources in KDE, that are not "readonly"). 265(It syncs will all resources in KDE, that are not "readonly").
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).
228Choose on the Z the menu: 271Choose on the Z the menu:
229Syncronize - <your name for the desktop sync profile> 272Syncronize - <your name for the desktop sync profile>
230( that was "BUG" in our example ). 273( that was "BUG" in our example ).
231That's all. 274That's all.
232 275
233Do the same with KA/Pi. 276Do the same with KA/Pi.
234 277
235NOTE: 278NOTE:
236If an appointment/addressee is created on the Z, it is added to the 279If an appointment/addressee is created on the Z, it is added to the
237standard resource in KDE. 280standard resource in KDE.
238 281
239If you have todos with subtodos in your calendar, you will get on 282If you have todos with subtodos in your calendar, you will get on
240every sync (after you restartet KOrganizer or Kontact in KDE) 283every sync (after you restartet KOrganizer or Kontact in KDE)
241the message "xx items changed on local", where 284the message "xx items changed on local", where
242xx is greater or equal to the number of todos. 285xx is greater or equal to the number of todos.
243That behaviour is caused by a bug in KDE. 286That 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
249 292
250 293
251 294