| -rw-r--r-- | bin/kdepim/SyncHowto.txt | 27 |
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,75 +1,76 @@ WARNING: YOU MAY GET UNEXSPECTED (I.E. WRONG) SYNCHRONIZATION RESULTS, IF YOU CHANGE AN EVENT ON THE FIRST DEVICE AND SYNC IMMEDIATELY FROM THE OTHER DEVICE WITH THIS DEVICE, IF THE CLOCKS OF THE TWO DEVICES HAVE TOO MUCH DIFFERENCE. -In other words: Please make shure, that the clocks of the devices +In other words: Please make sure, that the clocks of the devices you want to sync have only a difference of some seconds! CONTENT: 0) How syncing works 1) Qick overview of settings 2) Sync settings in sync dialog 3) Syncing background 4) Sync preferences 5) Details about sync profile kinds ************************************************************************* 0) How syncing works ************************************************************************* Note: The recommended and easiest way to syncronize two devices where -KO/Pi or KA/Pi is installed, is the profile kind "Pi-Sync". +KO/Pi, KA/Pi or PWM/Pi is installed, is the profile kind "Pi-Sync". Details about that in 5) b). -In KDE-Pim/Pi you can synchronize ( sync ) your calendar/addressbook -with another calendar/addressbook , by syncing your -(local) calendar/addressbook with a (remote) file. +In KDE-Pim/Pi you can synchronize ( sync ) your calendar/addressbook/ +passwordfile with another calendar/addressbook/passwordfile, +by syncing your (local) calendar/addressbook/passwordfile +with a (remote) file. This remote file may on your local filesystem or on another (remote) device. -If you want to sync with another remote device, -you have two create a sync profile. +If you want to sync with another remote device, you have to create +a sync profile. You have two choices for choosing the profil kind: -I) You have to choose profile kind "Remote file" and to specify a +I) You can choose profile kind "Remote file" and specify a command line download/upload command ( like scp, ftp, ...) to a) download the remote file to your local machine to a temp file b) sync with this temp file c) upload the synced file to the remote device -II) If you want to sync with a device, where KO/Pi( or KA/Pi ) is +II) If you want to sync with a device, where KO/Pi( or KA/Pi, PWM/Pi) is installed, you can easily get the remote file via network with the build in file transfer feature: Choose profile kind "Pi-Sync" and - a) Start KO/Pi or KA/Pi on remote device and + a) Start KO/Pi,KA/Pi or PWM/Pi on remote device and enable "Pi-Sync" on remote device with password and port. b) Specify password, port and IP address in your profile. You can sync with your mobile phone as well. Everything is explained in more details below. NOTE: If you do not use profile kind "Pi-Sync", it is recommended to close -a running KO/Pi ( or KA/Pi) on the remote device. -(Note: KO/Pi( or KA/Pi) running on Zaurus with +a running KO/Pi (KA/Pi, PWM/Pi) on the remote device. +(Note: KO/Pi(KA/Pi, PWM/Pi) running on Zaurus with FastLoad enabled will never be closed!) After syncing with a running KO/Pi on the remote device, a "save" on the remote device will tell you that it needs to merge (sync). After merging (just a syncing with the changed file) you will get the new data showing in remote KO/Pi. ************************************************************************* 1) Qick overview of settings ************************************************************************* a) Open sync settings dialog (Menu Synchronize - Configure...) b) Give your device a unique name. (unique in the set of all devices you want to sync with). If you have already configured another devive and created there a sync profile to sync with this device, give your device the same name as this sync profile! The same name is important, @@ -480,17 +481,17 @@ connection = fbusblue # | "1250" will force CP1250) or UTF8 (in Linux - "utf8") # ----------------|------------------------------------------------------------ # Logfile | Use, when want to have logfile from communication. # Logformat | What debug info and format should be used: # | "nothing" - no debug level (default) # | "text" - transmission dump in text format # | "textall" - all possible info in text format # | "errors" - errors in text format # | "binary" - transmission dump in binary format # ----------------|------------------------------------------------------------ # Use_Locking | under Unix/Linux use "yes", if want to lock used device # | to prevent using it by other applications. In win32 ignored -
\ No newline at end of file + |