summaryrefslogtreecommitdiffabout
path: root/bin
authorzautrix <zautrix>2004-10-13 03:13:22 (UTC)
committer zautrix <zautrix>2004-10-13 03:13:22 (UTC)
commit1b821cec88acdc0c3bc5a5498c8265eb480257b3 (patch) (unidiff)
tree3f5a04b400ab68bc0165d5fb7389f8b902eefb37 /bin
parent8f852fddc2dc5b63511d6ad1c85a1e74141969ff (diff)
downloadkdepimpi-1b821cec88acdc0c3bc5a5498c8265eb480257b3.zip
kdepimpi-1b821cec88acdc0c3bc5a5498c8265eb480257b3.tar.gz
kdepimpi-1b821cec88acdc0c3bc5a5498c8265eb480257b3.tar.bz2
updated sync howto
Diffstat (limited to 'bin') (more/less context) (show 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
@@ -224,48 +224,54 @@ SYNC PREFERENCES:
224 May be the most useful syncing mode. 224 May be the most useful syncing mode.
225 225
226 -Ask for every entry on conflict: 226 -Ask for every entry on conflict:
227 Pops up an event viewer dialog and 227 Pops up an event viewer dialog and
228 shows the two conflicting entries there. 228 shows the two conflicting entries there.
229 The user can chose, which entry he would like to take. 229 The user can chose, which entry he would like to take.
230 The button for the newest entry 230 The button for the newest entry
231 is automatically set as default button. 231 is automatically set as default button.
232 The color for the newest entry is green. 232 The color for the newest entry is green.
233 233
234 -Force: Take local entry always: 234 -Force: Take local entry always:
235 Even if the calendars are already synced 235 Even if the calendars are already synced
236 there is no item deleted on local. 236 there is no item deleted on local.
237 237
238 -Force: Take remote entry always: 238 -Force: Take remote entry always:
239 Analogous to 239 Analogous to
240 "Force: Take local entry always" 240 "Force: Take local entry always"
241 241
242************************************************************************* 242*************************************************************************
2435) Details about sync profile kinds 2435) Details about sync profile kinds
244************************************************************************* 244*************************************************************************
245 245
246a) Local file 246a) Local file
247 Please specify a local file you want to sync with. 247 Please specify a local file you want to sync with.
248 Note: If you are syncing a file, which is used by KA/Pi, please check the
249 "Addressbook file (*.vcf) is used by KA/Pi".
250 If you are syncing with a file from KAddressbook or another program,
251 please uncheck "Addressbook file (*.vcf) is used by KA/Pi".
252 To set this properly is important! KA/Pi uses a "last modified" property,
253 which is not supported by KAddressbook.
248 254
249b) Pi-Sync (direct Kx/Pi to Kx/Pi sync) 255b) Pi-Sync (direct Kx/Pi to Kx/Pi sync)
250 We mention here only KO/Pi, but the same is valid for KA/Pi. 256 We mention here only KO/Pi, but the same is valid for KA/Pi.
251 If you want to sync with a device, where KO/Pi is 257 If you want to sync with a device, where KO/Pi is
252 installed, you can easily get the remote file via network 258 installed, you can easily get the remote file via network
253 with the build in file transfer feature "Pi-Sync": 259 with the build in file transfer feature "Pi-Sync":
254 You have first to enable file transfer on the remote device: 260 You have first to enable file transfer on the remote device:
255 - Start KO/Pi on the remote device. 261 - Start KO/Pi on the remote device.
256 - Choose Menu Synchronize-Enable Pi-Sync. 262 - Choose Menu Synchronize-Enable Pi-Sync.
257 - Choose a port number, where KO/Pi should listen for 263 - Choose a port number, where KO/Pi should listen for
258 file sending requests. Valid port numbers are numbers 264 file sending requests. Valid port numbers are numbers
259 between 1 and 65565. Do not specify port numbers, that are 265 between 1 and 65565. Do not specify port numbers, that are
260 used by other applications. A port number between 9000 and 9999 266 used by other applications. A port number between 9000 and 9999
261 is most likely not used by another application. 267 is most likely not used by another application.
262 The default port number is 9197 for KO/Pi. 268 The default port number is 9197 for KO/Pi.
263 If you specify a port number, which is already in use, 269 If you specify a port number, which is already in use,
264 you will get an error message when closing this dialog. 270 you will get an error message when closing this dialog.
265 - Choose a password. 271 - Choose a password.
266 - Click OK. 272 - Click OK.
267 Now KO/Pi will send the calendar data via the network, 273 Now KO/Pi will send the calendar data via the network,
268 if some other device is sending a "please send calendar" 274 if some other device is sending a "please send calendar"
269 request on the given port using the given password. 275 request on the given port using the given password.
270 If you want to be sure, nobody can access your calendar 276 If you want to be sure, nobody can access your calendar
271 data, simply disable the file transfer feature on the 277 data, simply disable the file transfer feature on the
@@ -277,48 +283,55 @@ b) Pi-Sync (direct Kx/Pi to Kx/Pi sync)
277 (this may be the case, if you use DHCP for connection 283 (this may be the case, if you use DHCP for connection
278 of the remote device to the network) simply enable 284 of the remote device to the network) simply enable
279 "Ask for preferences before sync". 285 "Ask for preferences before sync".
280 Then you will be asked to confirm the 286 Then you will be asked to confirm the
281 "Pi-Sync" specific settings 287 "Pi-Sync" specific settings
282 (Password,IP address, port number) 288 (Password,IP address, port number)
283 and you can easily change the IP address before each sync. 289 and you can easily change the IP address before each sync.
284 290
285 On your local device, create a new profile and choose 291 On your local device, create a new profile and choose
286 profile kind "Pi-Sync". 292 profile kind "Pi-Sync".
287 Fill in the needed values: 293 Fill in the needed values:
288 - Password for remote access: 294 - Password for remote access:
289 The password you specified on the remote device. 295 The password you specified on the remote device.
290 - Remote IP address: 296 - Remote IP address:
291 The IP address of the remote device. 297 The IP address of the remote device.
292 - Remote port number: 298 - Remote port number:
293 The port number you specified on the remote device. 299 The port number you specified on the remote device.
294 300
295 Now you can syncronize your local device easily with your 301 Now you can syncronize your local device easily with your
296 remote device. This works well for all platforms KO/Pi is 302 remote device. This works well for all platforms KO/Pi is
297 running on, e.g. syncing a KO/Pi on Zaurus with KO/Pi on Windows 303 running on, e.g. syncing a KO/Pi on Zaurus with KO/Pi on Windows
298 is now very easy. 304 is now very easy.
299 305
300c) Remote file 306c) Remote file
307 Note: If you are syncing a file, which is used by KA/Pi, please check the
308 "Addressbook file (*.vcf) is used by KA/Pi".
309 If you are syncing with a file from KAddressbook or another program,
310 please uncheck "Addressbook file (*.vcf) is used by KA/Pi".
311 To set this properly is important! KA/Pi uses a "last modified" property,
312 which is not supported by KAddressbook.
313
301 Syncing with the profile kind "Remote file" is performed in three steps: 314 Syncing with the profile kind "Remote file" is performed in three steps:
302 i) download the remote file to your local machine to a temp file 315 i) download the remote file to your local machine to a temp file
303 ii) sync with this temp file 316 ii) sync with this temp file
304 iii) upload the synced file to the remote device 317 iii) upload the synced file to the remote device
305 318
306 The down-/uploading if i) and iii) is done via a command line command. 319 The down-/uploading if i) and iii) is done via a command line command.
307 Please specify the download/upload command ( like scp, ftp, ...) and the 320 Please specify the download/upload command ( like scp, ftp, ...) and the
308 file name of the temp file in the corresponding fields. 321 file name of the temp file in the corresponding fields.
309 322
310d) Mobile device (cell phone) 323d) Mobile device (cell phone)
311 Note: On the Zaurus you have to install the phoneaccess_xxx_arm.ipk package 324 Note: On the Zaurus you have to install the phoneaccess_xxx_arm.ipk package
312 to be able to access mobile phones. 325 to be able to access mobile phones.
313 We mention here only KO/Pi, but the same is valid for KA/Pi. 326 We mention here only KO/Pi, but the same is valid for KA/Pi.
314 Note: 327 Note:
315 It is only possible to sync a mobile phone with one particular device 328 It is only possible to sync a mobile phone with one particular device
316 running KO/Pi. If you want to be able to write data of more than one device 329 running KO/Pi. If you want to be able to write data of more than one device
317 to the mobile phone (e.g. from your Zaurus and from your Windows Laptop) 330 to the mobile phone (e.g. from your Zaurus and from your Windows Laptop)
318 do not sync with the mobile phone at all, but use the 331 do not sync with the mobile phone at all, but use the
319 "Export to phone" functionality from the different devices. 332 "Export to phone" functionality from the different devices.
320 Using "Export to phone" makes it not possible to get back data from the 333 Using "Export to phone" makes it not possible to get back data from the
321 phone, if it was changed there, of course. 334 phone, if it was changed there, of course.
322 If you sync with the phone, do not use "Export to phone" from any device. 335 If you sync with the phone, do not use "Export to phone" from any device.
323 (And do not sync, as mentioned above, from any other device with that phone). 336 (And do not sync, as mentioned above, from any other device with that phone).
324 It would delete the needed information for syncing with that phone! 337 It would delete the needed information for syncing with that phone!