summaryrefslogtreecommitdiffabout
authorzautrix <zautrix>2005-02-16 19:52:35 (UTC)
committer zautrix <zautrix>2005-02-16 19:52:35 (UTC)
commitebd0c1a894113262ff7c8ecc78261583b68e0907 (patch) (unidiff)
tree67403bfc439aae4a8bd47b1a0ec45b2569191b12
parentbb5f02a73778bf4623294390a31f1fb92aa95ff5 (diff)
downloadkdepimpi-ebd0c1a894113262ff7c8ecc78261583b68e0907.zip
kdepimpi-ebd0c1a894113262ff7c8ecc78261583b68e0907.tar.gz
kdepimpi-ebd0c1a894113262ff7c8ecc78261583b68e0907.tar.bz2
fixxx
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,117 +1,104 @@
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
82Start KO/Pi 69Start KO/Pi
83Choose menu: Synchronize - Enable PiSync 70Choose menu: Synchronize - Enable PiSync
84Leave port as the default 9197. 71Leave port as the default 9197.
85Choose password xyz. 72Choose password xyz.
86Click OK. 73Click OK.
87 74
88(ii) Linux laptop: 192.168.0.88: Name: BUG 75(ii) Linux laptop: 192.168.0.88: Name: BUG
89Start KO/Pi 76Start KO/Pi
90Choose menu: Synchronize - Enable PiSync 77Choose menu: Synchronize - Enable PiSync
91Leave port as the default 9197. 78Leave port as the default 9197.
92Check the box "Automatically sync with KDE-Desktop when receiving sync request". 79Check the box "Automatically sync with KDE-Desktop when receiving sync request".
93Choose password xyz. 80Choose password xyz.
94Click OK. 81Click OK.
95 82
96(iii) Zaurus: 192.168.129.201: Name: Z760 83(iii) Zaurus: 192.168.129.201: Name: Z760
97Start KO/Pi 84Start KO/Pi
98Choose menu: Synchronize - Enable PiSync 85Choose menu: Synchronize - Enable PiSync
99Leave port as the default 9197. 86Leave port as the default 9197.
100Choose password xyz. 87Choose password xyz.
101Click OK. 88Click OK.
102 89
103The configuration of the passive sync devices is done. 90The configuration of the passive sync devices is done.
104 91
105***************************************** 92*****************************************
106(2b) Configuring the aktive sync device: 93(2b) Configuring the aktive sync device:
107***************************************** 94*****************************************
108 95
109Linux desktop: 192.168.0.99: Name: K7 96Linux desktop: 192.168.0.99: Name: K7
110Start KO/Pi 97Start KO/Pi
111Choose menu: Synchronize - Configure... 98Choose menu: Synchronize - Configure...
112 99
113Set "Local device name" to "K7" 100Set "Local device name" to "K7"
114 101
115Choose profile: KDE_Desktop 102Choose profile: KDE_Desktop
116Check "Include in multiple calendar sync". 103Check "Include in multiple calendar sync".
117 104
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,114 +1,107 @@
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
45II) If you want to sync with a device, where KO/Pi( or KA/Pi, PWM/Pi) is 42II) 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
79 (A local device, that performs the sync, B remote device) 72 (A local device, that performs the sync, B remote device)
80 and then B->A. Such that the B->A sync knows about the 73 and then B->A. Such that the B->A sync knows about the
81 already performed A->B sync. 74 already performed A->B sync.
82 That means: It is unimportant if you sync A->B or B->A, 75 That means: It is unimportant if you sync A->B or B->A,
83 the devices A and B will be synced properly. 76 the devices A and B will be synced properly.
84c) Create a new sync profile and give it a unique name. 77c) Create a new sync profile and give it a unique name.
85 (unique in the set of all sync profiles on this device). 78 (unique in the set of all sync profiles on this device).
86 If you want to sync with a device, where KO/Pi is already installed 79 If you want to sync with a device, where KO/Pi is already installed
87 and which has a given unique device name, use this device name as 80 and which has a given unique device name, use this device name as
88 your profile name ( refer to b) ). 81 your profile name ( refer to b) ).
89d) Choose the profile kind of your syncing method: 82d) Choose the profile kind of your syncing method:
90 (i) Local file or 83 (i) Local file or
91 (ii) Pi-Sync or 84 (ii) Pi-Sync or
92 (iii) Remote file or 85 (iii) Remote file or
93 (iiii) Mobile Phone. 86 (iiii) Mobile Phone.
94 Detailed explanation in 6) 87 Detailed explanation in 6)
95e) Choose the other profile options. 88e) Choose the other profile options.
96 Detailed explanation in 2) 89 Detailed explanation in 2)
97f) Close sync dialog with OK. 90f) Close sync dialog with OK.
98g) Sync. 91g) Sync.
99 92
100NOTE: 93NOTE:
101AFTER SYNCING THERE ARE "SYNC EVENTS" CREATED 94AFTER SYNCING THERE ARE "SYNC EVENTS" CREATED
102(OR UPDATED, IF IT ALREADY EXITS) FOR EACH SYNC PROFILE. 95(OR UPDATED, IF IT ALREADY EXITS) FOR EACH SYNC PROFILE.
103YOU MAY NOT DELETE OR CHANGE THESE EVENTS. 96YOU MAY NOT DELETE OR CHANGE THESE EVENTS.
104 97
105************************************************************************* 98*************************************************************************
1062) Sync settings in sync dialog 992) Sync settings in sync dialog
107************************************************************************* 100*************************************************************************
108 101
109a) Local device name: 102a) Local device name:
110 -> 1) b) 103 -> 1) b)
111b) Profile: 104b) Profile:
112 -> 1) c) 105 -> 1) c)
113c) Multiple Sync options: Include in multiple sync: 106c) Multiple Sync options: Include in multiple sync:
114 In the Synchronize menu, there is a multiple sync menu entry. 107 In the Synchronize menu, there is a multiple sync menu entry.
@@ -160,213 +153,174 @@ h) Write back (on remote) existing entries only:
160 Check this to update the remote data only. 153 Check this to update the remote data only.
161 I.e. no data from yor local calendar/addressbook is added to the 154 I.e. no data from yor local calendar/addressbook is added to the
162 remote device. You may use this option to 155 remote device. You may use this option to
163 sync against some kind of "public calendar/addressbook" without 156 sync against some kind of "public calendar/addressbook" without
164 adding anything of your personal data. 157 adding anything of your personal data.
165 But in this case, you cannot add an item to the remoet device. 158 But in this case, you cannot add an item to the remoet device.
166i) Apply filter when adding data to remote: 159i) Apply filter when adding data to remote:
167 What is a filter? You can read this in -> 5) 160 What is a filter? You can read this in -> 5)
168 With this option you can specify a filter for events/contacts, 161 With this option you can specify a filter for events/contacts,
169 which should be added to the remote database, because they are 162 which should be added to the remote database, because they are
170 in the local database and not in the remote database. 163 in the local database and not in the remote database.
171 (Database = calendar file or addressbook file). 164 (Database = calendar file or addressbook file).
172 Note that the filter is NOT applied to the local 165 Note that the filter is NOT applied to the local
173 database before syncing. It is only applied to a particular 166 database before syncing. It is only applied to a particular
174 item of the local database which should be added to the remote database. 167 item of the local database which should be added to the remote database.
175 Well, but what is the difference? 168 Well, but what is the difference?
176 The differnce is: If the local database AND the remote database contain 169 The differnce is: If the local database AND the remote database contain
177 an already synced item, which does not match the filter, then this item is synced. 170 an already synced item, which does not match the filter, then this item is synced.
178 If the local database contains an item which does not match the filter 171 If the local database contains an item which does not match the filter
179 and the remote database does not contain this item, then this item is not added 172 and the remote database does not contain this item, then this item is not added
180 to the remote database, but it is still in the local database after syncing. 173 to the remote database, but it is still in the local database after syncing.
181 Example: 174 Example:
182 You have specified a calendar filter "only public events". 175 You have specified a calendar filter "only public events".
183 You specify this filter as the outgoing filter for syncing. 176 You specify this filter as the outgoing filter for syncing.
184 If there is an event in the local database which is not "public", but "private", 177 If there is an event in the local database which is not "public", but "private",
185 this event is not added to the remote database. 178 this event is not added to the remote database.
186 If there is an event in the local database and in the remote database which is 179 If there is an event in the local database and in the remote database which is
187 "private" (maybe added by someone else) then this event is synced and 180 "private" (maybe added by someone else) then this event is synced and
188 it is in the local database and in the remote database after syncing. 181 it is in the local database and in the remote database after syncing.
189 That means in particular you cannot remove an event from the remote 182 That means in particular you cannot remove an event from the remote
190 database but setting it to "private". 183 database but setting it to "private".
191 If you want to remove the event you can clone it, set it to private and delete the 184 If you want to remove the event you can clone it, set it to private and delete the
192 original event. Then the original event is deleted in the remote database after sync and 185 original event. Then the original event is deleted in the remote database after sync and
193 the cloned event is not added to the remote database, because it is private. 186 the cloned event is not added to the remote database, because it is private.
194j) Write back (calendar) entries for time period only: 187j) Write back (calendar) entries for time period only:
195 Check this to write back only calendar entries for a given time period. 188 Check this to write back only calendar entries for a given time period.
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:
266 Takes the remote entry on conflict. 234 Takes the remote entry on conflict.
267 If it is the first sync, 235 If it is the first sync,
268 "Ask for every entry" 236 "Ask for every entry"
269 is chosen automatically, 237 is chosen automatically,
270 if this is selected. 238 if this is selected.
271 239
272 -Take newest entry on conflict: 240 -Take newest entry on conflict:
273 This takes the newest entry on conflict. 241 This takes the newest entry on conflict.
274 May be the most useful syncing mode. 242 May be the most useful syncing mode.
275 243
276 -Ask for every entry on conflict: 244 -Ask for every entry on conflict:
277 Pops up an event viewer dialog and 245 Pops up an event viewer dialog and
278 shows the two conflicting entries there. 246 shows the two conflicting entries there.
279 The user can chose, which entry he would like to take. 247 The user can chose, which entry he would like to take.
280 The button for the newest entry 248 The button for the newest entry
281 is automatically set as default button. 249 is automatically set as default button.
282 The color for the newest entry is green. 250 The color for the newest entry is green.
283 251
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,
337 which is not supported by KAddressbook. 291 which is not supported by KAddressbook.
338 292
339b) Pi-Sync (direct Kx/Pi to Kx/Pi sync) 293b) Pi-Sync (direct Kx/Pi to Kx/Pi sync)
340 We mention here only KO/Pi, but the same is valid for KA/Pi. 294 We mention here only KO/Pi, but the same is valid for KA/Pi.
341 If you want to sync with a device, where KO/Pi is 295 If you want to sync with a device, where KO/Pi is
342 installed, you can easily get the remote file via network 296 installed, you can easily get the remote file via network
343 with the build in file transfer feature "Pi-Sync": 297 with the build in file transfer feature "Pi-Sync":
344 You have first to enable file transfer on the remote device: 298 You have first to enable file transfer on the remote device:
345 - Start KO/Pi on the remote device. 299 - Start KO/Pi on the remote device.
346 - Choose Menu Synchronize-Enable Pi-Sync. 300 - Choose Menu Synchronize-Enable Pi-Sync.
347 - Choose a port number, where KO/Pi should listen for 301 - Choose a port number, where KO/Pi should listen for
348 file sending requests. Valid port numbers are numbers 302 file sending requests. Valid port numbers are numbers
349 between 1 and 65565. Do not specify port numbers, that are 303 between 1 and 65565. Do not specify port numbers, that are
350 used by other applications. A port number between 9000 and 9999 304 used by other applications. A port number between 9000 and 9999
351 is most likely not used by another application. 305 is most likely not used by another application.
352 The default port number is 9197 for KO/Pi. 306 The default port number is 9197 for KO/Pi.
353 If you specify a port number, which is already in use, 307 If you specify a port number, which is already in use,
354 you will get an error message when closing this dialog. 308 you will get an error message when closing this dialog.
355 - Choose a password. 309 - Choose a password.
356 - Click OK. 310 - Click OK.
357 Now KO/Pi will send the calendar data via the network, 311 Now KO/Pi will send the calendar data via the network,
358 if some other device is sending a "please send calendar" 312 if some other device is sending a "please send calendar"
359 request on the given port using the given password. 313 request on the given port using the given password.
360 If you want to be sure, nobody can access your calendar 314 If you want to be sure, nobody can access your calendar
361 data, simply disable the file transfer feature on the 315 data, simply disable the file transfer feature on the
362 remote device after the syncing is done by choosing: 316 remote device after the syncing is done by choosing:
363 Menu Synchronize-Disable Pi-Sync. 317 Menu Synchronize-Disable Pi-Sync.
364 318
365 Note: If you want to sync with a remote device that gets different 319 Note: If you want to sync with a remote device that gets different
366 IPaddresses each time connected to the network 320 IPaddresses each time connected to the network
367 (this may be the case, if you use DHCP for connection 321 (this may be the case, if you use DHCP for connection
368 of the remote device to the network) simply enable 322 of the remote device to the network) simply enable
369 "Ask for preferences before sync". 323 "Ask for preferences before sync".
370 Then you will be asked to confirm the 324 Then you will be asked to confirm the
371 "Pi-Sync" specific settings 325 "Pi-Sync" specific settings
372 (Password,IP address, port number) 326 (Password,IP address, port number)
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
@@ -1,87 +1,88 @@
1Features of KO/Pi and hints for usage of KO/Pi 1Features of KO/Pi and hints for usage of KO/Pi
2(www.pi-sync.net) 2(www.pi-sync.net)
3 3
4A) General features 4A) General features
5 0) Main features 5 0) Main features
6 1) Import - export - connection - syncing 6 1) Import - export - connection - syncing
7 2) Filter 7 2) Filter
8 3) Managing categories: 8 3) Managing categories:
9 4) Cancelling of items: 9 4) Cancelling of items:
10 5) Addressbook access: 10 5) Addressbook access:
11 6) Quick editing: 11 6) Quick editing:
12 7) Fast navigation: 12 7) Fast navigation:
13 8) Printing: 13 8) Printing:
14 9) Configuration: 14 9) Configuration:
15 10) Language: 15 10) Language:
16 11) Alarm: 16 11) Alarm:
17 12) What'sThis Help: 17 12) What'sThis Help:
18 18
19B) Useful features, that are not straighforward to see 19B) Useful features, that are not straighforward to see
20 1) Right mouse click on Zaurus 20 1) Right mouse click on Zaurus
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 )
52 Via the search function you can send any number/selection of events/tasks/journal via infrared. 53 Via the search function you can send any number/selection of events/tasks/journal via infrared.
53Via the search function you can export and save any number/selection of events/tasks/journal to an ics file. 54Via the search function you can export and save any number/selection of events/tasks/journal to an ics file.
54Via the search function you can export and save any number/selection of journals and descriptions of events/todos to a plain text file. 55Via the search function you can export and save any number/selection of journals and descriptions of events/todos to a plain text file.
55KO/Pi can import xml calendar/todo data from Opie/old Qtopia environment. 56KO/Pi can import xml calendar/todo data from Opie/old Qtopia environment.
56KO/Pi can sync calendar/todo data with new Sharp Rom DTM model PIM applications, found on Zaurus 7x0/860 and Sharp Rom 3.1 (and above) for 5x00 series. 57KO/Pi can sync calendar/todo data with new Sharp Rom DTM model PIM applications, found on Zaurus 7x0/860 and Sharp Rom 3.1 (and above) for 5x00 series.
57(Hint: Rename /home/QtPalmtop/bin/datebook to e.g. /home/QtPalmtop/bin/datebookwech 58(Hint: Rename /home/QtPalmtop/bin/datebook to e.g. /home/QtPalmtop/bin/datebookwech
58to prevent alarm notification by the Sharp calendar app) 59to prevent alarm notification by the Sharp calendar app)
59KO/Pi can sync calendar/todo/journal data with any local ics file. 60KO/Pi can sync calendar/todo/journal data with any local ics file.
60In KO/Pi you can create a specific profile for each device to sync with. 61In KO/Pi you can create a specific profile for each device to sync with.
61 KO/Pi can automatically down/upload a remote ics file to a temp file via user specified system command (e.g. ssh/scp, ftp, ...) to sync with. 62 KO/Pi can automatically down/upload a remote ics file to a temp file via user specified system command (e.g. ssh/scp, ftp, ...) to sync with.
62 KO/Pi can ask you, if a conflict while syncing is detected and displays a detailed view of both events/todos. 63 KO/Pi can ask you, if a conflict while syncing is detected and displays a detailed view of both events/todos.
63 Multiple sync with many profiles at once is supported. Read "Multi Sync HowTo". 64 Multiple sync with many profiles at once is supported. Read "Multi Sync HowTo".
64 KO/Pi can sync after an easy and quick setup via network in the "Pi-Sync" mode with another running instance of KO/Pi with "Pi-Sync" enabled. 65 KO/Pi can sync after an easy and quick setup via network in the "Pi-Sync" mode with another running instance of KO/Pi with "Pi-Sync" enabled.
65 KO/Pi on Linux can sync with KDE calendar data. 66 KO/Pi on Linux can sync with KDE calendar data.
66 KO/Pi on the Zaurus can sync with KDE calendar data on desktop via Pi-Sync. Read "KDE-Sync HowTo". 67 KO/Pi on the Zaurus can sync with KDE calendar data on desktop via Pi-Sync. Read "KDE-Sync HowTo".
67 KO/Pi can sync and export data to mobile phones. Supported models are depending of the used lib, libgammu. 68 KO/Pi can sync and export data to mobile phones. Supported models are depending of the used lib, libgammu.
68 If KO/Pi detects that the saved file on disk has changed,(e.g. a remote sync from somewhere has happened), 69 If KO/Pi detects that the saved file on disk has changed,(e.g. a remote sync from somewhere has happened),
69 it asks you, if you want to overwrite the file or if you want to sync with the file. Such that no data is lost. 70 it asks you, if you want to overwrite the file or if you want to sync with the file. Such that no data is lost.
70KO/Pi can save/load templates for events/todos. 71KO/Pi can save/load templates for events/todos.
712) 722)
72Filter: 73Filter:
73You can define filters for displaying/not displaying specified categories. 74You can define filters for displaying/not displaying specified categories.
74Quick access to the first 20 filters via hotkeys 1-0 and <ctrl>1-0 75Quick access to the first 20 filters via hotkeys 1-0 and <ctrl>1-0
753) 763)
76Managing categories: 77Managing categories:
77After importing/loading/syncing there may be new categories in events or todos which are not in the category list. 78After importing/loading/syncing there may be new categories in events or todos which are not in the category list.
78 You can choose what to do with these categories: 79 You can choose what to do with these categories:
79 -Add to category list 80 -Add to category list
80 -Or remove them from events/todos 81 -Or remove them from events/todos
81In the list view/search dialog you can quickly assign categories to all selected items. 82In the list view/search dialog you can quickly assign categories to all selected items.
82 You can choose 83 You can choose
83 -to add a selection of categories to the list of categories 84 -to add a selection of categories to the list of categories
84 -to set a selection of categories as the new list of categories 85 -to set a selection of categories as the new list of categories
85You can specify a color to every categorie. 86You can specify a color to every categorie.
86 The events/tasks of this categorie are displayed with this color in the agenda view. 87 The events/tasks of this categorie are displayed with this color in the agenda view.
87 You can configure, if the events/tasks categorie color is shown in todo view/month view as well. 88 You can configure, if the events/tasks categorie color is shown in todo view/month view as well.