summaryrefslogtreecommitdiffabout
Unidiff
Diffstat (more/less context) (ignore whitespace changes)
-rw-r--r--bin/kdepim/MultiSyncHowTo.txt27
-rw-r--r--bin/kdepim/SyncHowto.txt102
-rw-r--r--bin/kdepim/korganizer/featuresKOPI.txt3
3 files changed, 37 insertions, 95 deletions
diff --git a/bin/kdepim/MultiSyncHowTo.txt b/bin/kdepim/MultiSyncHowTo.txt
index 3591eb9..05bd801 100644
--- a/bin/kdepim/MultiSyncHowTo.txt
+++ b/bin/kdepim/MultiSyncHowTo.txt
@@ -1,81 +1,68 @@
1Multi Sync HowTo 1Multi Sync HowTo
2 2
3With KDE-Pim/Pi you can sync several devices 3With KDE-Pim/Pi you can sync several devices "in one go". That means you choose on one device (where everything is confgured in the right way) "Multiple Sync" and all devices will be synced. All devices must be reachable via network.
4"in one go". That means you choose on one device
5(where everything is confgured in the right way)
6"Multiple Sync" and all devices will be synced.
7All devices must be reachable via network.
8 4
9In this HowTo we will give an explicit example what to set up 5In this HowTo we will give an explicit example what to set up and how configure.
10and how configure.
11 6
12We assume, that we have four devices which should be synced: 7We assume, that we have four devices which should be synced:
13A Sharp Zaurus PDA with KDE-Pim/Pi installed.. 8A Sharp Zaurus PDA with KDE-Pim/Pi installed..
14A Windows laptop with KDE-Pim/Pi installed. 9A Windows laptop with KDE-Pim/Pi installed.
15A Linux Desktop with KDE installed. 10A Linux Desktop with KDE installed.
16A Linux Laptop with KDE installed. 11A Linux Laptop with KDE installed.
17 12
18NOTE: Your KDE version must be 3.3.0 or higher for sncing with. 13NOTE: Your KDE version must be 3.3.0 or higher for sncing with.
19 Please read KDE Sync HowTo how to update your SuSE 9.1 to KDE 3.3.x 14 Please read KDE Sync HowTo how to update your SuSE 9.1 to KDE 3.3.x
20 (KDE Sync HowTo is available in the help menu of KO/Pi and KA/Pi). 15 (KDE Sync HowTo is available in the help menu of KO/Pi and KA/Pi).
21 16
22The Zaurus is connected to the Linux Desktop via USB cable. 17The Zaurus is connected to the Linux Desktop via USB cable.
23 18
24All calendar addressbook data should be synced with the other devices. 19All calendar addressbook data should be synced with the other devices. That means in particular, that the calendar/address data of KDE on the Linux laptop and desktop is synced with the other devices.
25That means in particular, that the calendar/address data of KDE on
26the Linux laptop and desktop is synced with the other devices.
27 20
28First we have to install the needed programs, 21First we have to install the needed programs, then we have to configure the programs.
29then we have to configure the programs.
30 22
31***************************************** 23*****************************************
32(1) Installing the programs: 24(1) Installing the programs:
33***************************************** 25*****************************************
34 26
35Download the files from 27Download the files from
36http://sourceforge.net/projects/kdepimpi/ 28http://sourceforge.net/projects/kdepimpi/
37project name KDE/Pim. 29project name KDE/Pim.
38Download the latest release. 30Download the latest release.
39You will find in every file a ReadMe, 31You will find in every file a ReadMe,
40where you can read how to install. 32where you can read how to install.
41(a) Installing KDE-Pim/Pi on the Windows laptop: 33(a) Installing KDE-Pim/Pi on the Windows laptop:
42 Download file kdepim_X.X.X_for_Windows.exe.zip 34 Download file kdepim_X.X.X_for_Windows.exe.zip
43(b) Installing KDE-Pim/Pi on the Linux laptop and desktop: 35(b) Installing KDE-Pim/Pi on the Linux laptop and desktop:
44 Download file KDE-Pim-Pi-1.9.10-SuSE9.1.i586.rpm.zip 36 Download file KDE-Pim-Pi-2.0.8-SuSE_9.2.i586.rpm.zip
45(c) Installing KDE-Pim/Pi on the Sharp Zaurus PDA: 37(c) Installing KDE-Pim/Pi on the Sharp Zaurus PDA:
46 Depending on your Rom: 38 Depending on your Rom:
47 Download file kdepim_X.X.X_for_SharpROM.ipk.zip 39 Download file kdepim_X.X.X_for_SharpROM.ipk.zip
48 or file kdepim_X.X.X_for_OZ-gcc3xx.ipk.zip for OpenZaurus users. 40 or file kdepim_X.X.X_for_OZ-gcc3xx.ipk.zip for OpenZaurus users.
49 If unsure, download kdepim_X.X.X_for_SharpROM.ipk.zip 41 If unsure, download kdepim_X.X.X_for_SharpROM.ipk.zip
50 42
51We assume that we have now on every device KDE-Pim/Pi installed. 43We assume that we have now on every device KDE-Pim/Pi installed.
52To learn more about syncing, please read now the 44To learn more about syncing, please read now the
53Sync HowTo 45Sync HowTo
54KDE Sync HowTo 46KDE Sync HowTo
55available in the help menu of KO/Pi and KA/Pi. 47available in the help menu of KO/Pi and KA/Pi.
56 48
57 49
58***************************************** 50*****************************************
59(2) Configuring KDE-Pim/Pi for Multiple sync: 51(2) Configuring KDE-Pim/Pi for Multiple sync:
60***************************************** 52*****************************************
61 53
62In mutiple sync, we have one aktive sync device and many 54In mutiple sync, we have one aktive sync device and many other passive sync devices.
63other passive sync devices.
64 55
65We use the Linux desktop as the active sync device. 56We use the Linux desktop as the active sync device. But there is no limitation. In general, you can choose any device as active sync device. The Zaurus is connected to the Linux Desktop via USB cable. Please read the KDE Sync HowTo to know how to set up this connection.
66But there is no limitation. In general, you can choose
67any device as active sync device.
68The Zaurus is connected to the Linux Desktop via USB cable.
69Please read the KDE Sync HowTo to know how to set up this connection.
70 57
71We assume, that the devices have the following IP numbers: 58We assume, that the devices have the following IP numbers:
72Windows laptop: 192.168.0.40 59Windows laptop: 192.168.0.40
73Linux laptop: 192.168.0.88 60Linux laptop: 192.168.0.88
74Zaurus: 192.168.129.201 61Zaurus: 192.168.129.201
75Linux desktop: 192.168.0.99 62Linux desktop: 192.168.0.99
76 63
77***************************************** 64*****************************************
78(2a) Configuring the passive sync devices: 65(2a) Configuring the passive sync devices:
79***************************************** 66*****************************************
80 67
81(i) Windows laptop: 192.168.0.40: Name: XP 68(i) Windows laptop: 192.168.0.40: Name: XP
diff --git a/bin/kdepim/SyncHowto.txt b/bin/kdepim/SyncHowto.txt
index b0473a1..a901616 100644
--- a/bin/kdepim/SyncHowto.txt
+++ b/bin/kdepim/SyncHowto.txt
@@ -1,44 +1,41 @@
1WARNING: 1WARNING:
2YOU MAY GET UNEXPECTED (I.E. WRONG) SYNCHRONIZATION RESULTS, 2YOU 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.
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
5HAVE TOO MUCH DIFFERENCE.
6 3
7In other words: Please make sure, that the clocks of the devices 4In other words: Please make sure, that the clocks of the devices you want to sync have only a difference of some seconds!
8you want to sync have only a difference of some seconds!
9 5
10 6
11CONTENT: 7CONTENT:
12 8
130) How syncing works 90) How syncing works
141) Qick overview of settings 101) Qick overview of settings
152) Sync settings in sync dialog 112) Sync settings in sync dialog
163) Syncing background 123) Syncing background
174) Sync preferences 134) Sync preferences
185) How a filter works 145) How a filter works
196) Details about sync profile kinds 156) Details about sync profile kinds
20 16
21************************************************************************* 17*************************************************************************
220) How syncing works 180) How syncing works
23************************************************************************* 19*************************************************************************
24 20
25Note: 21Note:
26The recommended and easiest way to syncronize two devices where 22The recommended and easiest way to syncronize two devices where KO/Pi, KA/Pi or PWM/Pi is installed, is the profile kind "Pi-Sync".
27KO/Pi, KA/Pi or PWM/Pi is installed, is the profile kind "Pi-Sync".
28Details about that in 6) b). 23Details about that in 6) b).
29 24
30In KDE-Pim/Pi you can synchronize ( sync ) your calendar/addressbook/ 25In KDE-Pim/Pi you can synchronize ( sync ) your
31passwordfile with another calendar/addressbook/passwordfile, 26calendar/addressbook/passwordfile with another c
32by syncing your (local) calendar/addressbook/passwordfile 27alendar/addressbook/passwordfile,
28by syncing your (local)
29calendar/addressbook/passwordfile
33with a (remote) file. 30with a (remote) file.
34This remote file may on your local filesystem 31This remote file may on your local filesystem
35or on another (remote) device. 32or on another (remote) device.
36 33
37If you want to sync with another remote device, you have to create 34If you want to sync with another remote device, you have to create
38a sync profile. 35a sync profile.
39You have two choices for choosing the profil kind: 36You have two choices for choosing the profil kind:
40I) You can choose profile kind "Remote file" and specify a 37I) You can choose profile kind "Remote file" and specify a
41 command line download/upload command ( like scp, ftp, ...) to 38 command line download/upload command ( like scp, ftp, ...) to
42 a) download the remote file to your local machine to a temp file 39 a) download the remote file to your local machine to a temp file
43 b) sync with this temp file 40 b) sync with this temp file
44 c) upload the synced file to the remote device 41 c) upload the synced file to the remote device
@@ -46,33 +43,29 @@ II) If you want to sync with a device, where KO/Pi( or KA/Pi, PWM/Pi) is
46 installed, you can easily get the remote file via network 43 installed, you can easily get the remote file via network
47 with the build in file transfer feature: 44 with the build in file transfer feature:
48 Choose profile kind "Pi-Sync" and 45 Choose profile kind "Pi-Sync" and
49 a) Start KO/Pi,KA/Pi or PWM/Pi on remote device and 46 a) Start KO/Pi,KA/Pi or PWM/Pi on remote device and
50 enable "Pi-Sync" on remote device with password and port. 47 enable "Pi-Sync" on remote device with password and port.
51 b) Specify password, port and IP address in your profile. 48 b) Specify password, port and IP address in your profile.
52 49
53 50
54You can sync with your mobile phone as well. 51You can sync with your mobile phone as well.
55Everything is explained in more details below. 52Everything is explained in more details below.
56 53
57NOTE: 54NOTE:
58If you do not use profile kind "Pi-Sync", 55If 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.
59it is recommended to close
60a running KO/Pi (KA/Pi, PWM/Pi) on the remote device.
61(Note: KO/Pi(KA/Pi, PWM/Pi) running on Zaurus with 56(Note: KO/Pi(KA/Pi, PWM/Pi) running on Zaurus with
62FastLoad enabled will never be closed!) 57FastLoad enabled will never be closed!)
63After syncing with a running KO/Pi on the remote device, 58After 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).
64a "save" on the remote device will tell you that it needs to merge (sync). 59After merging (just a syncing with the changed file) you will get the new data showing in remote KO/Pi.
65After merging (just a syncing with the changed file)
66you will get the new data showing in remote KO/Pi.
67 60
68************************************************************************* 61*************************************************************************
691) Qick overview of settings 621) Qick overview of settings
70************************************************************************* 63*************************************************************************
71 64
72a) Open sync settings dialog (Menu Synchronize - Configure...) 65a) Open sync settings dialog (Menu Synchronize - Configure...)
73b) Give your device a unique name. 66b) Give your device a unique name.
74 (unique in the set of all devices you want to sync with). 67 (unique in the set of all devices you want to sync with).
75 If you have already configured another devive and created 68 If you have already configured another devive and created
76 there a sync profile to sync with this device, give your device 69 there a sync profile to sync with this device, give your device
77 the same name as this sync profile! The same name is important, 70 the same name as this sync profile! The same name is important,
78 because it makes it possible to sync first A->B 71 because it makes it possible to sync first A->B
@@ -196,70 +189,45 @@ j) Write back (calendar) entries for time period only:
196 (Useful when syncing with mobile phones.) 189 (Useful when syncing with mobile phones.)
197 You can specify the date range in weeks for the weeks in the past to the weeks in the future. 190 You can specify the date range in weeks for the weeks in the past to the weeks in the future.
198 191
199k) Profile kind: 192k) Profile kind:
200 Details -> 6) 193 Details -> 6)
201 194
202************************************************************************* 195*************************************************************************
2033) Syncing background 1963) Syncing background
204************************************************************************* 197*************************************************************************
205 198
206The same mentioned for calendars is valid for addressbooks as well. 199The same mentioned for calendars is valid for addressbooks as well.
207 200
208Synchronizing calendars ( i.e. files ) means, 201Synchronizing calendars ( i.e. files ) means, to merge two calendars in a useful way. If the two calendars are completely different, there is no problem, the resulting calendar contains all data from the local and from the remote calendar.
209to merge two calendars in a useful way. 202
210If the two calendars are completely different, 203Problems will occur, if you have edited items from the local calendar on the remote machine. Then it could be, that items are in conflict. Two items are "in conflict", if they have the same unique ID (which get an item at time of creation and owns it until it is deleted ) and they both are modified after the last synchronization.
211there is no problem, the resulting calendar contains 204
212all data from the local and from the remote calendar. 205At first sync of two calendars there is no item deleted. If the calendars are synced before and there is an item, which is not edited after the last sync and is only available in one calendar, then this item is deleted in this calendar.
213
214Problems will occur, if you have edited items
215from the local calendar on the remote machine.
216Then it could be, that items are in conflict.
217Two items are "in conflict", if they have the
218same unique ID (which get an item at time of
219creation and owns it until it is deleted )
220and they both are modified after the last
221synchronization.
222
223At first sync of two calendars there is no item deleted.
224If the calendars are synced before and there is an item,
225which is not edited after the last sync and is only
226available in one calendar, then this item is deleted
227in this calendar.
228 206
229But when was the last synchronization between two calendars? 207But when was the last synchronization between two calendars?
230 208
231To know that, KO/Pi creates at first syncing 209To know that, KO/Pi creates at first syncing of two files an unique event "<profile name> - sync Event" 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.
232of two files an unique event "<profile name> - sync Event"
233on the remote and the local calendar.
234After syncing, the start time of this event is set
235to the time of syncing.
236The event is read only and the user may not change it.
237 210
238If two such files are synced, that both have an event 211If 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.
239"<profile name> - sync Event" and the events have
240the same start time, then deleted items on the one calendar
241are deleted on the other as well.
242 212
243 213
244************************************************************************* 214*************************************************************************
2454) Sync preferences 2154) Sync preferences
246************************************************************************* 216*************************************************************************
247 217
248Two items are "in conflict", if they have the same unique ID 218Two items are "in conflict", if they have the same unique ID and they both are modified after the last synchronization.
249and they both are modified after the last synchronization.
250(Details -> 3) ). 219(Details -> 3) ).
251 220
252If an item is not modified after the last sync and 221If an item is not modified after the last sync and it is not found in the other calendar, it is deleted.
253it is not found in the other calendar, it is deleted.
254 222
255On the first sync, there is no item deleted. 223On the first sync, there is no item deleted.
256 224
257SYNC PREFERENCES: 225SYNC PREFERENCES:
258 -Take local entry on conflict: 226 -Take local entry on conflict:
259 Takes the local entry on conflict. 227 Takes the local entry on conflict.
260 If it is the first sync, 228 If it is the first sync,
261 "Ask for every entry" 229 "Ask for every entry"
262 is chosen automatically, 230 is chosen automatically,
263 if this is selected. 231 if this is selected.
264 232
265 -Take remote entry on conflict: 233 -Take remote entry on conflict:
@@ -284,53 +252,39 @@ SYNC PREFERENCES:
284 -Force: Take local entry always: 252 -Force: Take local entry always:
285 Even if the calendars are already synced 253 Even if the calendars are already synced
286 there is no item deleted on local. 254 there is no item deleted on local.
287 255
288 -Force: Take remote entry always: 256 -Force: Take remote entry always:
289 Analogous to 257 Analogous to
290 "Force: Take local entry always" 258 "Force: Take local entry always"
291 259
292************************************************************************* 260*************************************************************************
2935) How a filter works 2615) How a filter works
294************************************************************************* 262*************************************************************************
295 263
296A filter is a rule to decide if a particular item 264A filter is a rule to decide if a particular item (calendar iten item or contact item) belongs to a set of items.
297(calendar iten item or contact item) belongs to a set of items.
298For example, you can specify a set as: 265For example, you can specify a set as:
299Only items, that belongs to that category. 266Only items, that belongs to that category.
300Or: Only items, that does not belong to that category. 267Or: Only items, that does not belong to that category.
301Or: Only items, that are public. 268Or: Only items, that are public.
302 269
303If you specify a filter in a syncing profile, you can set the 270If you specify a filter in a syncing profile, you can set the rules of adding items to the local or remote database.
304rules of adding items to the local or remote database.
305 271
306Example: 272Example:
307You have a public calendar in your company, which contains all 273You have a public calendar in your company, which contains all company relevant data.
308company relevant data. 274
309 275You have different projects in the company and for project specific events is always set the project name as a category:
310You have different projects in the company and for project specific events 276E.g. all events of the project PRO_ABC do have set the categorie PRO_ABC. But you are not interested in events of PRO_ABC, because you are not working on it. Then you can specify a filter: All, but not with categoroy PRO_ABC. When you specify this filter as an incoming filter for your sync profile, all events of the company are synced and added to your local calendar, but not the evenst of the project PRO_ABC.
311is always set the project name as a category: 277
312E.g. all events of the project PRO_ABC do have set the categorie PRO_ABC. 278You do not want that your private data can be seen in the public calendar of your company. Well, set the property to "private" for all your private data and specify an outgoing filter: Only " public" and "confidential". Then you can sync your personal calendar with the calendar of the company, but your private data is not added to the public calendar.
313But you are not interested in events of PRO_ABC, because you are not working on it.
314Then you can specify a filter: All, but not with categoroy PRO_ABC.
315When you specify this filter as an incoming filter for your sync profile,
316all events of the company are synced and added to your local calendar, but not
317the evenst of the project PRO_ABC.
318
319You do not want that your private data can be seen
320in the public calendar of your company.
321Well, set the property to "private" for all your private data
322and specify an outgoing filter: Only " public" and "confidential".
323Then you can sync your personal calendar with the calendar of the company,
324but your private data is not added to the public calendar.
325 279
326************************************************************************* 280*************************************************************************
3276) Details about sync profile kinds 2816) Details about sync profile kinds
328************************************************************************* 282*************************************************************************
329 283
330a) Local file 284a) Local file
331 Please specify a local file you want to sync with. 285 Please specify a local file you want to sync with.
332 Note: If you are syncing a file, which is used by KA/Pi, please check the 286 Note: If you are syncing a file, which is used by KA/Pi, please check the
333 "Addressbook file (*.vcf) is used by KA/Pi". 287 "Addressbook file (*.vcf) is used by KA/Pi".
334 If you are syncing with a file from KAddressbook or another program, 288 If you are syncing with a file from KAddressbook or another program,
335 please uncheck "Addressbook file (*.vcf) is used by KA/Pi". 289 please uncheck "Addressbook file (*.vcf) is used by KA/Pi".
336 To set this properly is important! KA/Pi uses a "last modified" property, 290 To set this properly is important! KA/Pi uses a "last modified" property,
diff --git a/bin/kdepim/korganizer/featuresKOPI.txt b/bin/kdepim/korganizer/featuresKOPI.txt
index dc10a6b..283ec8e 100644
--- a/bin/kdepim/korganizer/featuresKOPI.txt
+++ b/bin/kdepim/korganizer/featuresKOPI.txt
@@ -21,31 +21,32 @@ B) Useful features, that are not straighforward to see
21 2) Moving of items in the agenda view 21 2) Moving of items in the agenda view
22 3) Creating exceptions for recurring events 22 3) Creating exceptions for recurring events
23 4) Navigation in month view 23 4) Navigation in month view
24 5) Navigation in agenda view 24 5) Navigation in agenda view
25 6) Monthview as week view 25 6) Monthview as week view
26 7) Switching display mode in date edit 26 7) Switching display mode in date edit
27 8) Recurring todos 27 8) Recurring todos
28 28
29 29
30****************************************************** 30******************************************************
31A) General features 31A) General features
32****************************************************** 32******************************************************
33Features of KO/Pi 1.9.12: 33Features of KO/Pi 2.0.8:
340) 340)
35Main features: 35Main features:
36KO/Pi makes synchronizing your data easy! 36KO/Pi makes synchronizing your data easy!
37Details in 1) and the sync HowTos. 37Details in 1) and the sync HowTos.
38With KO/Pi you can manage your events/todos/journals. 38With KO/Pi you can manage your events/todos/journals.
39Todos may have subtodos. 39Todos may have subtodos.
40Todos may recur ( details: B)8) Recurring todos)
40A subtodo can be changed to a parent root todo. 41A subtodo can be changed to a parent root todo.
41A (sub)todo can be reparented to make it a subtodo of another todo. 42A (sub)todo can be reparented to make it a subtodo of another todo.
42KO/Pi has a monthview, a What's Next view, an event list view, a small and big todo-view and an agenda view to display 1-42 days. 43KO/Pi has a monthview, a What's Next view, an event list view, a small and big todo-view and an agenda view to display 1-42 days.
43KO/Pi is Qt-only based and runs on Sharp Zaurus PDA, Linux and Windows. 44KO/Pi is Qt-only based and runs on Sharp Zaurus PDA, Linux and Windows.
441) 451)
45Import - export - connection - syncing: 46Import - export - connection - syncing:
46KO/Pi on Windows can import calendar data easyly from Outlook directly via OLE. 47KO/Pi on Windows can import calendar data easyly from Outlook directly via OLE.
47 Recurring events with exceptions and attendee lists of meetings are imported properly. 48 Recurring events with exceptions and attendee lists of meetings are imported properly.
48KO/Pi can import/export ics and vcs files. 49KO/Pi can import/export ics and vcs files.
49KO/Pi can save/load ics backup files. 50KO/Pi can save/load ics backup files.
50KO/Pi can send ics and vcs files via infrared, with and without timezone settings.( Zaurus only ) 51KO/Pi can send ics and vcs files via infrared, with and without timezone settings.( Zaurus only )
51KO/Pi can receive files via infrared directly, after beam receive is enabled.( Zaurus only ) 52KO/Pi can receive files via infrared directly, after beam receive is enabled.( Zaurus only )