summaryrefslogtreecommitdiffabout
Side-by-side diff
Diffstat (more/less context) (ignore whitespace changes)
-rw-r--r--bin/kdepim/SyncHowto.txt13
1 files changed, 13 insertions, 0 deletions
diff --git a/bin/kdepim/SyncHowto.txt b/bin/kdepim/SyncHowto.txt
index 3cab446..ec5513a 100644
--- a/bin/kdepim/SyncHowto.txt
+++ b/bin/kdepim/SyncHowto.txt
@@ -184,181 +184,194 @@ on the remote and the local calendar.
After syncing, the start time of this event is set
to the time of syncing.
The event is read only and the user may not change it.
If two such files are synced, that both have an event
"<profile name> - sync Event" and the events have
the same start time, then deleted items on the one calendar
are deleted on the other as well.
*************************************************************************
4) Sync preferences
*************************************************************************
Two items are "in conflict", if they have the same unique ID
and they both are modified after the last synchronization.
(Details -> 3) ).
If an item is not modified after the last sync and
it is not found in the other calendar, it is deleted.
On the first sync, there is no item deleted.
SYNC PREFERENCES:
-Take local entry on conflict:
Takes the local entry on conflict.
If it is the first sync,
"Ask for every entry"
is chosen automatically,
if this is selected.
-Take remote entry on conflict:
Takes the remote entry on conflict.
If it is the first sync,
"Ask for every entry"
is chosen automatically,
if this is selected.
-Take newest entry on conflict:
This takes the newest entry on conflict.
May be the most useful syncing mode.
-Ask for every entry on conflict:
Pops up an event viewer dialog and
shows the two conflicting entries there.
The user can chose, which entry he would like to take.
The button for the newest entry
is automatically set as default button.
The color for the newest entry is green.
-Force: Take local entry always:
Even if the calendars are already synced
there is no item deleted on local.
-Force: Take remote entry always:
Analogous to
"Force: Take local entry always"
*************************************************************************
5) Details about sync profile kinds
*************************************************************************
a) Local file
Please specify a local file you want to sync with.
+ Note: If you are syncing a file, which is used by KA/Pi, please check the
+ "Addressbook file (*.vcf) is used by KA/Pi".
+ If you are syncing with a file from KAddressbook or another program,
+ please uncheck "Addressbook file (*.vcf) is used by KA/Pi".
+ To set this properly is important! KA/Pi uses a "last modified" property,
+ which is not supported by KAddressbook.
b) Pi-Sync (direct Kx/Pi to Kx/Pi sync)
We mention here only KO/Pi, but the same is valid for KA/Pi.
If you want to sync with a device, where KO/Pi is
installed, you can easily get the remote file via network
with the build in file transfer feature "Pi-Sync":
You have first to enable file transfer on the remote device:
- Start KO/Pi on the remote device.
- Choose Menu Synchronize-Enable Pi-Sync.
- Choose a port number, where KO/Pi should listen for
file sending requests. Valid port numbers are numbers
between 1 and 65565. Do not specify port numbers, that are
used by other applications. A port number between 9000 and 9999
is most likely not used by another application.
The default port number is 9197 for KO/Pi.
If you specify a port number, which is already in use,
you will get an error message when closing this dialog.
- Choose a password.
- Click OK.
Now KO/Pi will send the calendar data via the network,
if some other device is sending a "please send calendar"
request on the given port using the given password.
If you want to be sure, nobody can access your calendar
data, simply disable the file transfer feature on the
remote device after the syncing is done by choosing:
Menu Synchronize-Disable Pi-Sync.
Note: If you want to sync with a remote device that gets different
IPaddresses each time connected to the network
(this may be the case, if you use DHCP for connection
of the remote device to the network) simply enable
"Ask for preferences before sync".
Then you will be asked to confirm the
"Pi-Sync" specific settings
(Password,IP address, port number)
and you can easily change the IP address before each sync.
On your local device, create a new profile and choose
profile kind "Pi-Sync".
Fill in the needed values:
- Password for remote access:
The password you specified on the remote device.
- Remote IP address:
The IP address of the remote device.
- Remote port number:
The port number you specified on the remote device.
Now you can syncronize your local device easily with your
remote device. This works well for all platforms KO/Pi is
running on, e.g. syncing a KO/Pi on Zaurus with KO/Pi on Windows
is now very easy.
c) Remote file
+ Note: If you are syncing a file, which is used by KA/Pi, please check the
+ "Addressbook file (*.vcf) is used by KA/Pi".
+ If you are syncing with a file from KAddressbook or another program,
+ please uncheck "Addressbook file (*.vcf) is used by KA/Pi".
+ To set this properly is important! KA/Pi uses a "last modified" property,
+ which is not supported by KAddressbook.
+
Syncing with the profile kind "Remote file" is performed in three steps:
i) download the remote file to your local machine to a temp file
ii) sync with this temp file
iii) upload the synced file to the remote device
The down-/uploading if i) and iii) is done via a command line command.
Please specify the download/upload command ( like scp, ftp, ...) and the
file name of the temp file in the corresponding fields.
d) Mobile device (cell phone)
Note: On the Zaurus you have to install the phoneaccess_xxx_arm.ipk package
to be able to access mobile phones.
We mention here only KO/Pi, but the same is valid for KA/Pi.
Note:
It is only possible to sync a mobile phone with one particular device
running KO/Pi. If you want to be able to write data of more than one device
to the mobile phone (e.g. from your Zaurus and from your Windows Laptop)
do not sync with the mobile phone at all, but use the
"Export to phone" functionality from the different devices.
Using "Export to phone" makes it not possible to get back data from the
phone, if it was changed there, of course.
If you sync with the phone, do not use "Export to phone" from any device.
(And do not sync, as mentioned above, from any other device with that phone).
It would delete the needed information for syncing with that phone!
We are using Gammu (Version: 0.98.9) ( http://freshmeat.net/projects/gammu/ )
for accessing the phones.
Note: You cannot use the original Gammu for syncing KDE-Pim/Pi, because
we have modified the original version to make it useable for syncing!
Gammu allows access to many phones in many ways (Irda, Bluetooth, serial,...).
The recommended phone access using Gammu with KDE-Pim/Pi is Irda (infrared).
Bluetooth access is disabled on the Zaurus, but may work on Windows.
Please look at the Gammu homepage and documentation about more details
configuring Gammu how to access your phone.
If you have problems accessing your phone, start KO/Pi from the konsole
and you will get a more detailed output what went wrong.
About Gammu from the Gammu homepage:
Gammu (formerly known as MyGnokii2) is a cellular
manager for various mobile phones/modems.
It supports the Nokia 2100, 3100, 32xx, 33xx,
3410, 35xx, 51xx, 5210, 5510, 61xx, 62xx,
63xx, 6510, 6610, 6800, 71xx, 7210, 7250,
7250i, 82xx, 83xx, 8910, 9110, 9210
and compatible and AT devices (Siemens, Alcatel,
Falcom, WaveCom, IPAQ, Samsung, SE, and others)
over cables/infrared/BlueTooth.
Here is an example what to specify to access a Nokia 6310i via infrared:
On Linux (Zaurus):
I/O device: /dev/ircomm
Connection: irda
Model: <leave empty>
On Windows:
I/O device: <ignored - i.e. leave empty>
Connection: irda
Model: <leave empty>
Here is the overview from the Gammu documentation,
how to specify the connection settings for
I/O device:
Connection:
Model: