summaryrefslogtreecommitdiffabout
Unidiff
Diffstat (more/less context) (ignore whitespace changes)
-rw-r--r--bin/kdepim/korganizer/howtoSYNC.txt341
1 files changed, 305 insertions, 36 deletions
diff --git a/bin/kdepim/korganizer/howtoSYNC.txt b/bin/kdepim/korganizer/howtoSYNC.txt
index e73709b..ad765d3 100644
--- a/bin/kdepim/korganizer/howtoSYNC.txt
+++ b/bin/kdepim/korganizer/howtoSYNC.txt
@@ -1,9 +1,12 @@
1NOTE: 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
8you want to sync have only a difference of some seconds!
9
7 10
8CONTENT: 11CONTENT:
9 12
@@ -12,27 +15,48 @@ CONTENT:
122) Sync settings in sync dialog 152) Sync settings in sync dialog
133) Syncing background 163) Syncing background
144) Sync preferences 174) Sync preferences
185) Details about sync profile kinds
15 19
16************************************************************************* 20*************************************************************************
170) How syncing works 210) How syncing works
18************************************************************************* 22*************************************************************************
19 23
20In KO/Pi you can synchronize ( sync ) your calendar 24Note:
21with another calendar, by syncing your (local) calendar with a 25The recommended and easiest way to syncronize two devices where
22(remote) file. This remote file may on your local filesystem 26KO/Pi or KA/Pi is installed, is the profile kind "Pi-Sync".
27Details about that in 5) b).
28
29In KDE-Pim/Pi you can synchronize ( sync ) your calendar/addressbook
30with another calendar/addressbook , by syncing your
31(local) calendar/addressbook with a (remote) file.
32This remote file may on your local filesystem
23or on another (remote) device. 33or on another (remote) device.
24If it is on another device, you have to specify a
25command line download/upload command ( like scp, ftp, ...) to
26a) download the remote file to your local machine to a temp file
27b) sync with this temp file
28c) upload the synced file to the remote device
29 34
30You should create for every device, to sync with, a sync profile. 35If you want to sync with another remote device,
36you have two create a sync profile.
37You have two choices for choosing the profil kind:
38I) You have to choose profile kind "Remote file" and to specify a
39 command line download/upload command ( like scp, ftp, ...) to
40 a) download the remote file to your local machine to a temp file
41 b) sync with this temp file
42 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
44 installed, you can easily get the remote file via network
45 with the build in file transfer feature:
46 Choose profile kind "Pi-Sync" and
47 a) Start KO/Pi or KA/Pi on remote device and
48 enable "Pi-Sync" on remote device with password and port.
49 b) Specify password, port and IP address in your profile.
50
51
52You can sync with your mobile phone as well.
53Everything is explained in more details below.
31 54
32NOTE: 55NOTE:
33Before syncing, it is recommended to close 56If you do not use profile kind "Pi-Sync",
34a running KO/Pi on the remote device. 57it is recommended to close
35(Note: KO/Pi running on Zaurus with 58a running KO/Pi ( or KA/Pi) on the remote device.
59(Note: KO/Pi( or KA/Pi) running on Zaurus with
36FastLoad enabled will never be closed!) 60FastLoad enabled will never be closed!)
37After syncing with a running KO/Pi on the remote device, 61After syncing with a running KO/Pi on the remote device,
38a "save" on the remote device will tell you that it needs to merge (sync). 62a "save" on the remote device will tell you that it needs to merge (sync).
@@ -43,29 +67,33 @@ you will get the new data showing in remote KO/Pi.
431) Qick overview of settings 671) Qick overview of settings
44************************************************************************* 68*************************************************************************
45 69
46a) Open sync settings dialog 70a) Open sync settings dialog (Menu Synchronize - Configure...)
47b) Give your device a unique name. 71b) Give your device a unique name.
48 (unique in the set of all devices you want to sync with). 72 (unique in the set of all devices you want to sync with).
49 If you have already configured another devive and created 73 If you have already configured another devive and created
50 there a sync profile to sync with this device, give your device 74 there a sync profile to sync with this device, give your device
51 the same name as this sync profile! The same name is important! 75 the same name as this sync profile! The same name is important,
76 because it makes it possible to sync first A->B
77 (A local device, that performs the sync, B remote device)
78 and then B->A. Such that the B->A sync knows about the
79 already performed A->B sync.
80 That means: It is unimportant if you sync A->B or B->A,
81 the devices A and B will be synced properly.
52c) Create a new sync profile and give it a unique name. 82c) Create a new sync profile and give it a unique name.
53 (unique in the set of all sync profiles on this device). 83 (unique in the set of all sync profiles on this device).
54 If you want to sync with a device, where KO/Pi is already installed 84 If you want to sync with a device, where KO/Pi is already installed
55 and which has a given unique device name, use this device name as 85 and which has a given unique device name, use this device name as
56 your profile name. 86 your profile name ( refer to b) ).
57d) Coose the profile kind of your syncing method: 87d) Coose the profile kind of your syncing method:
58 (i) Local file or 88 (i) Local file or
59 (ii) Remote file 89 (ii) Pi-Sync or
60c) If you did choose (i), 90 (iii) Remote file or
61 specify the file name you want to sync with. 91 (iiii) Mobile Phone.
62 If you did choose (ii), 92 Detailed explanation in 5)
63 specify the system (command line) 93e) Choose the other profile options.
64 download/upload command of the remote file. 94 Detailed explanation in 2)
65d) Choose the other profile options. 95f) Close sync dialog with OK.
66 Detailed explanation in 2.) 96g) Sync.
67e) Close sync dialog with OK.
68f) Sync.
69 97
70NOTE: 98NOTE:
71AFTER SYNCING THERE ARE "SYNC EVENTS" CREATED 99AFTER SYNCING THERE ARE "SYNC EVENTS" CREATED
@@ -94,23 +122,34 @@ e) Sync preferences:
94f) Show summary after sync: 122f) Show summary after sync:
95 Check this to get a small summary dialog after sync 123 Check this to get a small summary dialog after sync
96 about number of added/changed/deleted events on local/remote. 124 about number of added/changed/deleted events on local/remote.
97g) Write back existing entries only: 125g) Write back synced data:
98 Check this to update the remote calendar only. 126 Uncheck this to update the local calendar only.
99 I.e. no event/todo from yor local calendar is added to the
100 remote calendar. You may use this option to
101 sync against some kind of "public calendar" without
102 writing back your personal data.
103h) Write back file:
104 Check this to update the local calendar only.
105 I.e. your local calendar is synced with the remote calendar 127 I.e. your local calendar is synced with the remote calendar
106 but nothing on the remote calendar is changed. 128 but nothing on the remote calendar is changed.
107i) Profile kind: 129 If you uncheck "Write back synced data", the settings
108 -> 1) d) 130 under h) and i) are ignored, of course.
131h) --Write back (on remote) existing entries only:
132 Check this to update the remote data only.
133 I.e. no data from yor local calendar/addressbook is added to the
134 remote device. You may use this option to
135 sync against some kind of "public calendar/addressbook" without
136 writing back your personal data.
137i) --Write back (calendar) entries in future only:
138 Check this to write back only calendar entries in future.
139 (Useful when syncing with mobile phones.)
140 You can specify the date range in weeks with
141 ---- Max. weeks in future.
142 Note: The date range starts always 7 days before the actual date!
143 I.e. the calendar events of the last week are written back always.
144j) Profile kind:
145 Details -> 5)
109 146
110************************************************************************* 147*************************************************************************
1113) Syncing background 1483) Syncing background
112************************************************************************* 149*************************************************************************
113 150
151The same mentioned for calendars is valid for addressbooks as well.
152
114Synchronizing calendars ( i.e. files ) means, 153Synchronizing calendars ( i.e. files ) means,
115to merge two calendars in a useful way. 154to merge two calendars in a useful way.
116If the two calendars are completely different, 155If the two calendars are completely different,
@@ -195,3 +234,233 @@ SYNC PREFERENCES:
195 Analogous to 234 Analogous to
196 "Force: Take local entry always" 235 "Force: Take local entry always"
197 236
237*************************************************************************
2385) Details about sync profile kinds
239*************************************************************************
240
241a) Local file
242 Please specify a local file you want to sync with.
243
244b) Pi-Sync (direct Kx/Pi to Kx/Pi sync)
245 We mention here only KO/Pi, but the same is valid for KA/Pi.
246 If you want to sync with a device, where KO/Pi is
247 installed, you can easily get the remote file via network
248 with the build in file transfer feature "Pi-Sync":
249 You have first to enable file transfer on the remote device:
250 - Start KO/Pi on the remote device.
251 - Choose Menu Synchronize-Enable Pi-Sync.
252 - Choose a port number, where KO/Pi should listen for
253 file sending requests. Valid port numbers are numbers
254 between 1 and 65565. Do not specify port numbers, that are
255 used by other applications. A port number between 9000 and 9999
256 is most likely not used by another application.
257 The default port number is 9197 for KO/Pi.
258 If you specify a port number, which is already in use,
259 you will get an error message when closing this dialog.
260 - Choose a password.
261 - Click OK.
262 Now KO/Pi will send the calendar data via the network,
263 if some other device is sending a "please send calendar"
264 request on the given port using the given password.
265 If you want to be sure, nobody can access your calendar
266 data, simply disable the file transfer feature on the
267 remote device after the syncing is done by choosing:
268 Menu Synchronize-Disable Pi-Sync.
269
270 On your local device, create a new profile and choose
271 profile kind "Pi-Sync".
272 Fill in the needed values:
273 - Password for remote access:
274 The password you specified on the remote device.
275 - Remote IP address:
276 The IP address of the remote device.
277 - Remote port number:
278 The port number you specified on the remote device.
279
280 Now you can syncronize your local device easily with your
281 remote device. This works well for all platforms KO/Pi is
282 running on, e.g. syncing a KO/Pi on Zaurus with KO/Pi on Windows
283 is now very easy.
284
285c) Remote file
286 Syncing with the profile kind "Remote file" is performed in three steps:
287 i) download the remote file to your local machine to a temp file
288 ii) sync with this temp file
289 iii) upload the synced file to the remote device
290
291 The down-/uploading if i) and iii) is done via a command line command.
292 Please specify the download/upload command ( like scp, ftp, ...) and the
293 file name of the temp file in the corresponding fields.
294
295d) Mobile device (cell phone)
296 We mention here only KO/Pi, but the same is valid for KA/Pi.
297 Note:
298 It is only possible to sync a mobile phone with one particular device
299 running KO/Pi. If you want to be able to write data of more than one device
300 to the mobile phone (e.g. from your Zaurus and from your Windows Laptop)
301 do not sync with the mobile phone at all, but use the
302 "Export to phone" functionality from the different devices.
303 Using "Export to phone" makes it not possible to get back data from the
304 phone, if it was changed there, of course.
305 If you sync with the phone, do not use "Export to phone" from any device.
306 (And do not sync, as mentioned above, from any other device with that phone).
307 It would delete the needed information for syncing with that phone!
308
309 We are using Gammu (Version: 0.98.9) ( http://freshmeat.net/projects/gammu/ )
310 for accessing the phones.
311 Note: You cannot use the original Gammu for syncing KDE-Pim/Pi, because
312 we have modified the original version to make it useable for syncing!
313 Gammu allows access to many phones in many ways (Irda, Bluetooth, serial,...).
314 The recommended phone access using Gammu with KDE-Pim/Pi is Irda (infrared).
315 Bluetooth access is disabled on the Zaurus, but may work on Windows.
316 Please look at the Gammu homepage and documentation about more details
317 configuring Gammu how to access your phone.
318 If you have problems accessing your phone, start KO/Pi from the konsole
319 and you will get a more detailed output what went wrong.
320 About Gammu from the Gammu homepage:
321 Gammu (formerly known as MyGnokii2) is a cellular
322 manager for various mobile phones/modems.
323 It supports the Nokia 2100, 3100, 32xx, 33xx,
324 3410, 35xx, 51xx, 5210, 5510, 61xx, 62xx,
325 63xx, 6510, 6610, 6800, 71xx, 7210, 7250,
326 7250i, 82xx, 83xx, 8910, 9110, 9210
327 and compatible and AT devices (Siemens, Alcatel,
328 Falcom, WaveCom, IPAQ, Samsung, SE, and others)
329 over cables/infrared/BlueTooth.
330
331 Here is an example what to specify to access a Nokia 6310i via infrared:
332 On Linux (Zaurus):
333 I/O device: /dev/ircomm
334 Connection: irda
335 Model: <leave empty>
336
337 On Windows:
338 I/O device: <ignored - i.e. leave empty>
339 Connection: irda
340 Model: <leave empty>
341
342 Here is the overview from the Gammu documentation,
343 how to specify the connection settings for
344 I/O device:
345 Connection:
346 Model:
347
348 Note: The documentation uses the term "port",
349 where we use the term "I/O device".
350 Note: You do not have to create/change the gammurc configuration file.
351 That will do KO/Pi for you.
352 Note: For a known model, leave "Model:" always empty,
353 such that Gammu can auto detect the model.
354
355# This is a sample ~/.gammurc file.
356# In Unix/Linux copy it into your home directory and name it .gammurc
357# or into /etc and name it gammurc
358# In Win32 copy it into directory with Gammu.exe and name gammurc
359# More about parameters later
360# -----------------------------------------------------------------------------
361
362[gammu]
363
364port = com8:
365#model = 6110
366connection = fbusblue
367#synchronizetime = yes
368#logfile = gammulog
369#logformat = textall
370#use_locking = yes
371#gammuloc = locfile
372#startinfo = yes
373#gammucoding = utf8
374
375[gammu1]
376
377port = com8:
378#model = 6110
379connection = fbusblue
380#synchronizetime = yes
381#logfile = gammulog
382#logformat = textall
383#use_locking = yes
384#gammuloc = locfile
385#startinfo = yes
386#gammucoding = utf8
387
388# -----------------------------------------------------------------------------
389# Now info about "Connection" parameter and connected with it port type
390# (more about port types later)
391# -----------------------------------------------------------------------------
392# "Connection" parameter | Port type | More details
393# -----------------------|-----------|-----------------------------------------
394# "fbus" | serial | Nokia FBUS2
395# "fbusirda"/"infrared" | serial | Nokia FBUS2 over direct infrared device
396# "fbusdlr3"/"dlr3" | serial | Nokia FBUS2 with DLR3 cable
397# "fbusdku5" | dku5 | Nokia FBUS2 with DKU5 cable. WIN32 ONLY
398# "fbuspl2303" | usb | Nokia FBUS2 with USB cable based on
399# | | PL2303 chip.
400# "fbusblue" | serial | Nokia FBUS2 over Bluetooth serial device
401# "phonetblue" | serial | Nokia PHONET FBUS over Bluetooth serial
402# | | device
403# "mrouterblue" | serial |
404# "mbus" | serial | Nokia MBUS2
405# "at19200"/"at115200"/..| serial | AT commands.8 bits, None parity, 1 stop
406# | | bit, no flow control
407# -----------------------|-----------|-----------------------------------------
408# "irdaphonet"/"irda" | irda | Nokia PHONET FBUS over socket infrared
409# "irdaat" | irda | AT commands with socket infrared
410# "irdaobex" | irda | OBEX over socket infrared. MODEL "obex"
411# -----------------------|-----------|-----------------------------------------
412# "bluephonet" | BT | Nokia PHONET FBUS with Bluetooth stack
413# "bluefbus"/"dlr3blue" | BT | Nokia FBUS2 with Bluetooth stack
414# "blueat"/"atblue" | BT | AT commands with Bluetooth stack
415# "blueobex" | BT | OBEX with Bluetooth. MODEL "obex"
416#
417# Now more about port types and connected with it "Port" parameter
418# -----------------------------------------------------------------------------
419# Port type | "Port" parameter in Windows/DOS | "Port" parameter in Linux/Unix
420# ----------|---------------------------------|--------------------------------
421# serial | "com*:" | "/dev/ttyS*"
422# | (example "com1:") | (example "/dev/ttyS1")
423# | | or "/dev/tts/**" (with DevFS)
424# ----------|---------------------------------|--------------------------------
425# irda | ignored (can be empty) | "/dev/ircomm*"
426# ----------|---------------------------------|--------------------------------
427# BT | Bluetooth device address
428# | (example "")
429# ----------|---------------------------------|--------------------------------
430# dku5 | ignored (can be empty) | connection with it not possible
431# ----------|---------------------------------|--------------------------------
432# usb | connection with it not possible | "/dev/ttyUSB*"
433#
434# Other config parameters
435# -----------------------------------------------------------------------------
436# Parameter name | Description
437# ----------------|------------------------------------------------------------
438# Model | use only, when Gammu doesn't recognize your phone model.
439# | Put it here. Example values: "6110", "6150", "6210", "8210"
440# SynchronizeTime | if you want to set time from computer to phone during
441# | starting connection. Do not rather use this option when
442# | when to reset phone during connection (in some phones need
443# | to set time again after restart)
444# GammuLoc | name of localisation file
445# StartInfo | this option allow to set, that you want (setting "yes")
446# | to see message on the phone screen or phone should enable
447# | light for a moment during starting connection. Phone
448# | WON'T beep during starting connection with this option.
449# GammuCoding | forces using specified codepage (in win32 - for example
450# | "1250" will force CP1250) or UTF8 (in Linux - "utf8")
451# ----------------|------------------------------------------------------------
452# Logfile | Use, when want to have logfile from communication.
453# Logformat | What debug info and format should be used:
454# | "nothing" - no debug level (default)
455# | "text" - transmission dump in text format
456# | "textall" - all possible info in text format
457# | "errors" - errors in text format
458# | "binary" - transmission dump in binary format
459# ----------------|------------------------------------------------------------
460# Use_Locking | under Unix/Linux use "yes", if want to lock used device
461# | to prevent using it by other applications. In win32 ignored
462
463
464
465
466 \ No newline at end of file