summaryrefslogtreecommitdiffabout
authorulf69 <ulf69>2004-10-22 22:32:54 (UTC)
committer ulf69 <ulf69>2004-10-22 22:32:54 (UTC)
commitbcad4a526b3bc04a4889e6bbbe9b73731a5aacf5 (patch) (unidiff)
tree6cc7ceb9829e6e2412fd1320b9292ec443a8d21b
parent6b99c0feac04963f814a32586268ecac966f3d51 (diff)
downloadkdepimpi-bcad4a526b3bc04a4889e6bbbe9b73731a5aacf5.zip
kdepimpi-bcad4a526b3bc04a4889e6bbbe9b73731a5aacf5.tar.gz
kdepimpi-bcad4a526b3bc04a4889e6bbbe9b73731a5aacf5.tar.bz2
added references to PWM/Pi
Diffstat (more/less context) (ignore whitespace changes)
-rw-r--r--bin/kdepim/SyncHowto.txt27
1 files changed, 14 insertions, 13 deletions
diff --git a/bin/kdepim/SyncHowto.txt b/bin/kdepim/SyncHowto.txt
index ec5513a..5874fc3 100644
--- a/bin/kdepim/SyncHowto.txt
+++ b/bin/kdepim/SyncHowto.txt
@@ -1,13 +1,13 @@
1WARNING: 1WARNING:
2YOU MAY GET UNEXSPECTED (I.E. WRONG) SYNCHRONIZATION RESULTS, 2YOU MAY GET UNEXSPECTED (I.E. WRONG) SYNCHRONIZATION RESULTS,
3IF YOU CHANGE AN EVENT ON THE FIRST DEVICE AND SYNC IMMEDIATELY FROM 3IF YOU CHANGE AN EVENT ON THE FIRST DEVICE AND SYNC IMMEDIATELY FROM
4THE OTHER DEVICE WITH THIS DEVICE, IF THE CLOCKS OF THE TWO DEVICES 4THE OTHER DEVICE WITH THIS DEVICE, IF THE CLOCKS OF THE TWO DEVICES
5HAVE TOO MUCH DIFFERENCE. 5HAVE TOO MUCH DIFFERENCE.
6 6
7In other words: Please make shure, that the clocks of the devices 7In other words: Please make sure, that the clocks of the devices
8you want to sync have only a difference of some seconds! 8you want to sync have only a difference of some seconds!
9 9
10 10
11CONTENT: 11CONTENT:
12 12
130) How syncing works 130) How syncing works
@@ -20,46 +20,47 @@ CONTENT:
20************************************************************************* 20*************************************************************************
210) How syncing works 210) How syncing works
22************************************************************************* 22*************************************************************************
23 23
24Note: 24Note:
25The recommended and easiest way to syncronize two devices where 25The recommended and easiest way to syncronize two devices where
26KO/Pi or KA/Pi is installed, is the profile kind "Pi-Sync". 26KO/Pi, KA/Pi or PWM/Pi is installed, is the profile kind "Pi-Sync".
27Details about that in 5) b). 27Details about that in 5) b).
28 28
29In KDE-Pim/Pi you can synchronize ( sync ) your calendar/addressbook 29In KDE-Pim/Pi you can synchronize ( sync ) your calendar/addressbook/
30with another calendar/addressbook , by syncing your 30passwordfile with another calendar/addressbook/passwordfile,
31(local) calendar/addressbook with a (remote) file. 31by syncing your (local) calendar/addressbook/passwordfile
32with a (remote) file.
32This remote file may on your local filesystem 33This remote file may on your local filesystem
33or on another (remote) device. 34or on another (remote) device.
34 35
35If you want to sync with another remote device, 36If you want to sync with another remote device, you have to create
36you have two create a sync profile. 37a sync profile.
37You have two choices for choosing the profil kind: 38You have two choices for choosing the profil kind:
38I) You have to choose profile kind "Remote file" and to specify a 39I) You can choose profile kind "Remote file" and specify a
39 command line download/upload command ( like scp, ftp, ...) to 40 command line download/upload command ( like scp, ftp, ...) to
40 a) download the remote file to your local machine to a temp file 41 a) download the remote file to your local machine to a temp file
41 b) sync with this temp file 42 b) sync with this temp file
42 c) upload the synced file to the remote device 43 c) upload the synced file to the remote device
43II) If you want to sync with a device, where KO/Pi( or KA/Pi ) is 44II) If you want to sync with a device, where KO/Pi( or KA/Pi, PWM/Pi) is
44 installed, you can easily get the remote file via network 45 installed, you can easily get the remote file via network
45 with the build in file transfer feature: 46 with the build in file transfer feature:
46 Choose profile kind "Pi-Sync" and 47 Choose profile kind "Pi-Sync" and
47 a) Start KO/Pi or KA/Pi on remote device and 48 a) Start KO/Pi,KA/Pi or PWM/Pi on remote device and
48 enable "Pi-Sync" on remote device with password and port. 49 enable "Pi-Sync" on remote device with password and port.
49 b) Specify password, port and IP address in your profile. 50 b) Specify password, port and IP address in your profile.
50 51
51 52
52You can sync with your mobile phone as well. 53You can sync with your mobile phone as well.
53Everything is explained in more details below. 54Everything is explained in more details below.
54 55
55NOTE: 56NOTE:
56If you do not use profile kind "Pi-Sync", 57If you do not use profile kind "Pi-Sync",
57it is recommended to close 58it is recommended to close
58a running KO/Pi ( or KA/Pi) on the remote device. 59a running KO/Pi (KA/Pi, PWM/Pi) on the remote device.
59(Note: KO/Pi( or KA/Pi) running on Zaurus with 60(Note: KO/Pi(KA/Pi, PWM/Pi) running on Zaurus with
60FastLoad enabled will never be closed!) 61FastLoad enabled will never be closed!)
61After syncing with a running KO/Pi on the remote device, 62After syncing with a running KO/Pi on the remote device,
62a "save" on the remote device will tell you that it needs to merge (sync). 63a "save" on the remote device will tell you that it needs to merge (sync).
63After merging (just a syncing with the changed file) 64After merging (just a syncing with the changed file)
64you will get the new data showing in remote KO/Pi. 65you will get the new data showing in remote KO/Pi.
65 66
@@ -490,7 +491,7 @@ connection = fbusblue
490# Use_Locking | under Unix/Linux use "yes", if want to lock used device 491# Use_Locking | under Unix/Linux use "yes", if want to lock used device
491# | to prevent using it by other applications. In win32 ignored 492# | to prevent using it by other applications. In win32 ignored
492 493
493 494
494 495
495 496
496 \ No newline at end of file 497