| -rw-r--r-- | bin/kdepim/SyncHowto.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/bin/kdepim/SyncHowto.txt b/bin/kdepim/SyncHowto.txt index 64f6f14..b0473a1 100644 --- a/bin/kdepim/SyncHowto.txt +++ b/bin/kdepim/SyncHowto.txt @@ -1,185 +1,185 @@ WARNING: YOU MAY GET UNEXPECTED (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 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) How a filter works 6) Details about sync profile kinds ************************************************************************* 0) How syncing works ************************************************************************* Note: The recommended and easiest way to syncronize two devices where KO/Pi, KA/Pi or PWM/Pi is installed, is the profile kind "Pi-Sync". Details about that in 6) b). 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 to create a sync profile. You have two choices for choosing the profil kind: 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, 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,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 (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, because it makes it possible to sync first A->B (A local device, that performs the sync, B remote device) and then B->A. Such that the B->A sync knows about the already performed A->B sync. That means: It is unimportant if you sync A->B or B->A, the devices A and B will be synced properly. c) Create a new sync profile and give it a unique name. (unique in the set of all sync profiles on this device). If you want to sync with a device, where KO/Pi is already installed and which has a given unique device name, use this device name as your profile name ( refer to b) ). -d) Coose the profile kind of your syncing method: +d) Choose the profile kind of your syncing method: (i) Local file or (ii) Pi-Sync or (iii) Remote file or (iiii) Mobile Phone. Detailed explanation in 6) e) Choose the other profile options. Detailed explanation in 2) f) Close sync dialog with OK. g) Sync. NOTE: AFTER SYNCING THERE ARE "SYNC EVENTS" CREATED (OR UPDATED, IF IT ALREADY EXITS) FOR EACH SYNC PROFILE. YOU MAY NOT DELETE OR CHANGE THESE EVENTS. ************************************************************************* 2) Sync settings in sync dialog ************************************************************************* a) Local device name: -> 1) b) b) Profile: -> 1) c) c) Multiple Sync options: Include in multiple sync: In the Synchronize menu, there is a multiple sync menu entry. If you choose this menu entry, all user defined profiles with this 'Include in multiple sync' option enabled will be synced one after another. And this twice. This will take some time. After that sync, on all devices should be the same data. d)- j) Sync algo options: d) Ask for preferences before sync: Check this to be asked for "Sync preferences" settings before each sync. If the profile kind is "Pi-Sync" you will be asked to confirm the "Pi-Sync" specific settings (Password,IP address, port number) as well. That makes it possible to use that profile for a device that is connected via DHCP to the network and gets different IP addresses when connecting to the network. e) Sync preferences: Choose here your sync preferences. Details -> 4) f) Show summary after sync: Check this to get a small summary dialog after sync about number of added/changed/deleted events on local/remote. g) Apply filter when adding data to local: What is a filter? You can read this in -> 5) With this option you can specify a filter for events/contacts, which should be added to the local database, because they are in the remote database and not in the local database. (Database = calendar file or addressbook file). Note that the filter is NOT applied to the remote database before syncing. It is only applied to a particular item which should be added to the local database. Well, but what is the difference? The differnce is: If the remote database AND the local database contain an already synced item, which does not match the filter, then this item is synced. If the remote database contains an item which does not match the filter and the local database does not contain this item, then this item is not added to the local database, but it is still in the remote database after syncing. g) Write back synced data: Uncheck this to update the local calendar only. I.e. your local calendar is synced with the remote calendar but nothing on the remote calendar is changed. If you uncheck "Write back synced data", the settings under h) and i) are ignored, of course. h) - j) Write back options: h) Write back (on remote) existing entries only: Check this to update the remote data only. I.e. no data from yor local calendar/addressbook is added to the remote device. You may use this option to sync against some kind of "public calendar/addressbook" without adding anything of your personal data. But in this case, you cannot add an item to the remoet device. i) Apply filter when adding data to remote: What is a filter? You can read this in -> 5) With this option you can specify a filter for events/contacts, which should be added to the remote database, because they are in the local database and not in the remote database. (Database = calendar file or addressbook file). Note that the filter is NOT applied to the local database before syncing. It is only applied to a particular item of the local database which should be added to the remote database. Well, but what is the difference? The differnce is: If the local database AND the remote database contain an already synced item, which does not match the filter, then this item is synced. If the local database contains an item which does not match the filter and the remote database does not contain this item, then this item is not added to the remote database, but it is still in the local database after syncing. Example: You have specified a calendar filter "only public events". You specify this filter as the outgoing filter for syncing. If there is an event in the local database which is not "public", but "private", this event is not added to the remote database. |