author | zautrix <zautrix> | 2005-02-16 19:52:35 (UTC) |
---|---|---|
committer | zautrix <zautrix> | 2005-02-16 19:52:35 (UTC) |
commit | ebd0c1a894113262ff7c8ecc78261583b68e0907 (patch) (unidiff) | |
tree | 67403bfc439aae4a8bd47b1a0ec45b2569191b12 /bin/kdepim | |
parent | bb5f02a73778bf4623294390a31f1fb92aa95ff5 (diff) | |
download | kdepimpi-ebd0c1a894113262ff7c8ecc78261583b68e0907.zip kdepimpi-ebd0c1a894113262ff7c8ecc78261583b68e0907.tar.gz kdepimpi-ebd0c1a894113262ff7c8ecc78261583b68e0907.tar.bz2 |
fixxx
-rw-r--r-- | bin/kdepim/MultiSyncHowTo.txt | 27 | ||||
-rw-r--r-- | bin/kdepim/SyncHowto.txt | 102 | ||||
-rw-r--r-- | bin/kdepim/korganizer/featuresKOPI.txt | 3 |
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,14 +1,9 @@ | |||
1 | Multi Sync HowTo | 1 | Multi Sync HowTo |
2 | 2 | ||
3 | With KDE-Pim/Pi you can sync several devices | 3 | With 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. | ||
7 | All devices must be reachable via network. | ||
8 | 4 | ||
9 | In this HowTo we will give an explicit example what to set up | 5 | In this HowTo we will give an explicit example what to set up and how configure. |
10 | and how configure. | ||
11 | 6 | ||
12 | We assume, that we have four devices which should be synced: | 7 | We assume, that we have four devices which should be synced: |
13 | A Sharp Zaurus PDA with KDE-Pim/Pi installed.. | 8 | A Sharp Zaurus PDA with KDE-Pim/Pi installed.. |
14 | A Windows laptop with KDE-Pim/Pi installed. | 9 | A Windows laptop with KDE-Pim/Pi installed. |
@@ -20,14 +15,11 @@ NOTE: Your KDE version must be 3.3.0 or higher for sncing with. | |||
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 | ||
22 | The Zaurus is connected to the Linux Desktop via USB cable. | 17 | The Zaurus is connected to the Linux Desktop via USB cable. |
23 | 18 | ||
24 | All calendar addressbook data should be synced with the other devices. | 19 | All 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. |
25 | That means in particular, that the calendar/address data of KDE on | ||
26 | the Linux laptop and desktop is synced with the other devices. | ||
27 | 20 | ||
28 | First we have to install the needed programs, | 21 | First we have to install the needed programs, then we have to configure the programs. |
29 | then we have to configure the programs. | ||
30 | 22 | ||
31 | ***************************************** | 23 | ***************************************** |
32 | (1) Installing the programs: | 24 | (1) Installing the programs: |
33 | ***************************************** | 25 | ***************************************** |
@@ -40,9 +32,9 @@ You will find in every file a ReadMe, | |||
40 | where you can read how to install. | 32 | where 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. |
@@ -58,16 +50,11 @@ available in the help menu of KO/Pi and KA/Pi. | |||
58 | ***************************************** | 50 | ***************************************** |
59 | (2) Configuring KDE-Pim/Pi for Multiple sync: | 51 | (2) Configuring KDE-Pim/Pi for Multiple sync: |
60 | ***************************************** | 52 | ***************************************** |
61 | 53 | ||
62 | In mutiple sync, we have one aktive sync device and many | 54 | In mutiple sync, we have one aktive sync device and many other passive sync devices. |
63 | other passive sync devices. | ||
64 | 55 | ||
65 | We use the Linux desktop as the active sync device. | 56 | We 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. |
66 | But there is no limitation. In general, you can choose | ||
67 | any device as active sync device. | ||
68 | The Zaurus is connected to the Linux Desktop via USB cable. | ||
69 | Please read the KDE Sync HowTo to know how to set up this connection. | ||
70 | 57 | ||
71 | We assume, that the devices have the following IP numbers: | 58 | We assume, that the devices have the following IP numbers: |
72 | Windows laptop: 192.168.0.40 | 59 | Windows laptop: 192.168.0.40 |
73 | Linux laptop: 192.168.0.88 | 60 | Linux laptop: 192.168.0.88 |
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,12 +1,8 @@ | |||
1 | WARNING: | 1 | WARNING: |
2 | YOU MAY GET UNEXPECTED (I.E. WRONG) SYNCHRONIZATION RESULTS, | 2 | YOU 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. |
3 | IF YOU CHANGE AN EVENT ON THE FIRST DEVICE AND SYNC IMMEDIATELY FROM | ||
4 | THE OTHER DEVICE WITH THIS DEVICE, IF THE CLOCKS OF THE TWO DEVICES | ||
5 | HAVE TOO MUCH DIFFERENCE. | ||
6 | 3 | ||
7 | In other words: Please make sure, that the clocks of the devices | 4 | In other words: Please make sure, that the clocks of the devices you want to sync have only a difference of some seconds! |
8 | you want to sync have only a difference of some seconds! | ||
9 | 5 | ||
10 | 6 | ||
11 | CONTENT: | 7 | CONTENT: |
12 | 8 | ||
@@ -22,15 +18,16 @@ CONTENT: | |||
22 | 0) How syncing works | 18 | 0) How syncing works |
23 | ************************************************************************* | 19 | ************************************************************************* |
24 | 20 | ||
25 | Note: | 21 | Note: |
26 | The recommended and easiest way to syncronize two devices where | 22 | The recommended and easiest way to syncronize two devices where KO/Pi, KA/Pi or PWM/Pi is installed, is the profile kind "Pi-Sync". |
27 | KO/Pi, KA/Pi or PWM/Pi is installed, is the profile kind "Pi-Sync". | ||
28 | Details about that in 6) b). | 23 | Details about that in 6) b). |
29 | 24 | ||
30 | In KDE-Pim/Pi you can synchronize ( sync ) your calendar/addressbook/ | 25 | In KDE-Pim/Pi you can synchronize ( sync ) your |
31 | passwordfile with another calendar/addressbook/passwordfile, | 26 | calendar/addressbook/passwordfile with another c |
32 | by syncing your (local) calendar/addressbook/passwordfile | 27 | alendar/addressbook/passwordfile, |
28 | by syncing your (local) | ||
29 | calendar/addressbook/passwordfile | ||
33 | with a (remote) file. | 30 | with a (remote) file. |
34 | This remote file may on your local filesystem | 31 | This remote file may on your local filesystem |
35 | or on another (remote) device. | 32 | or on another (remote) device. |
36 | 33 | ||
@@ -54,17 +51,13 @@ II) If you want to sync with a device, where KO/Pi( or KA/Pi, PWM/Pi) is | |||
54 | You can sync with your mobile phone as well. | 51 | You can sync with your mobile phone as well. |
55 | Everything is explained in more details below. | 52 | Everything is explained in more details below. |
56 | 53 | ||
57 | NOTE: | 54 | NOTE: |
58 | If you do not use profile kind "Pi-Sync", | 55 | If 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. |
59 | it is recommended to close | ||
60 | a 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 |
62 | FastLoad enabled will never be closed!) | 57 | FastLoad enabled will never be closed!) |
63 | After syncing with a running KO/Pi on the remote device, | 58 | After 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). |
64 | a "save" on the remote device will tell you that it needs to merge (sync). | 59 | After merging (just a syncing with the changed file) you will get the new data showing in remote KO/Pi. |
65 | After merging (just a syncing with the changed file) | ||
66 | you will get the new data showing in remote KO/Pi. | ||
67 | 60 | ||
68 | ************************************************************************* | 61 | ************************************************************************* |
69 | 1) Qick overview of settings | 62 | 1) Qick overview of settings |
70 | ************************************************************************* | 63 | ************************************************************************* |
@@ -204,54 +197,29 @@ k) Profile kind: | |||
204 | ************************************************************************* | 197 | ************************************************************************* |
205 | 198 | ||
206 | The same mentioned for calendars is valid for addressbooks as well. | 199 | The same mentioned for calendars is valid for addressbooks as well. |
207 | 200 | ||
208 | Synchronizing calendars ( i.e. files ) means, | 201 | Synchronizing 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. |
209 | to merge two calendars in a useful way. | 202 | |
210 | If the two calendars are completely different, | 203 | Problems 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. |
211 | there is no problem, the resulting calendar contains | 204 | |
212 | all data from the local and from the remote calendar. | 205 | At 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 | |||
214 | Problems will occur, if you have edited items | ||
215 | from the local calendar on the remote machine. | ||
216 | Then it could be, that items are in conflict. | ||
217 | Two items are "in conflict", if they have the | ||
218 | same unique ID (which get an item at time of | ||
219 | creation and owns it until it is deleted ) | ||
220 | and they both are modified after the last | ||
221 | synchronization. | ||
222 | |||
223 | At first sync of two calendars there is no item deleted. | ||
224 | If the calendars are synced before and there is an item, | ||
225 | which is not edited after the last sync and is only | ||
226 | available in one calendar, then this item is deleted | ||
227 | in this calendar. | ||
228 | 206 | ||
229 | But when was the last synchronization between two calendars? | 207 | But when was the last synchronization between two calendars? |
230 | 208 | ||
231 | To know that, KO/Pi creates at first syncing | 209 | To 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. |
232 | of two files an unique event "<profile name> - sync Event" | ||
233 | on the remote and the local calendar. | ||
234 | After syncing, the start time of this event is set | ||
235 | to the time of syncing. | ||
236 | The event is read only and the user may not change it. | ||
237 | 210 | ||
238 | If two such files are synced, that both have an event | 211 | If two such files are synced, that both have an event "<profile name> - sync Event" and the events have the same start time, then deleted items on the one calendar are deleted on the other as well. |
239 | "<profile name> - sync Event" and the events have | ||
240 | the same start time, then deleted items on the one calendar | ||
241 | are deleted on the other as well. | ||
242 | 212 | ||
243 | 213 | ||
244 | ************************************************************************* | 214 | ************************************************************************* |
245 | 4) Sync preferences | 215 | 4) Sync preferences |
246 | ************************************************************************* | 216 | ************************************************************************* |
247 | 217 | ||
248 | Two items are "in conflict", if they have the same unique ID | 218 | Two items are "in conflict", if they have the same unique ID and they both are modified after the last synchronization. |
249 | and they both are modified after the last synchronization. | ||
250 | (Details -> 3) ). | 219 | (Details -> 3) ). |
251 | 220 | ||
252 | If an item is not modified after the last sync and | 221 | If an item is not modified after the last sync and it is not found in the other calendar, it is deleted. |
253 | it is not found in the other calendar, it is deleted. | ||
254 | 222 | ||
255 | On the first sync, there is no item deleted. | 223 | On the first sync, there is no item deleted. |
256 | 224 | ||
257 | SYNC PREFERENCES: | 225 | SYNC PREFERENCES: |
@@ -292,37 +260,23 @@ SYNC PREFERENCES: | |||
292 | ************************************************************************* | 260 | ************************************************************************* |
293 | 5) How a filter works | 261 | 5) How a filter works |
294 | ************************************************************************* | 262 | ************************************************************************* |
295 | 263 | ||
296 | A filter is a rule to decide if a particular item | 264 | A 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. | ||
298 | For example, you can specify a set as: | 265 | For example, you can specify a set as: |
299 | Only items, that belongs to that category. | 266 | Only items, that belongs to that category. |
300 | Or: Only items, that does not belong to that category. | 267 | Or: Only items, that does not belong to that category. |
301 | Or: Only items, that are public. | 268 | Or: Only items, that are public. |
302 | 269 | ||
303 | If you specify a filter in a syncing profile, you can set the | 270 | If you specify a filter in a syncing profile, you can set the rules of adding items to the local or remote database. |
304 | rules of adding items to the local or remote database. | ||
305 | 271 | ||
306 | Example: | 272 | Example: |
307 | You have a public calendar in your company, which contains all | 273 | You have a public calendar in your company, which contains all company relevant data. |
308 | company relevant data. | 274 | |
309 | 275 | You have different projects in the company and for project specific events is always set the project name as a category: | |
310 | You have different projects in the company and for project specific events | 276 | E.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. |
311 | is always set the project name as a category: | 277 | |
312 | E.g. all events of the project PRO_ABC do have set the categorie PRO_ABC. | 278 | You 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. |
313 | But you are not interested in events of PRO_ABC, because you are not working on it. | ||
314 | Then you can specify a filter: All, but not with categoroy PRO_ABC. | ||
315 | When you specify this filter as an incoming filter for your sync profile, | ||
316 | all events of the company are synced and added to your local calendar, but not | ||
317 | the evenst of the project PRO_ABC. | ||
318 | |||
319 | You do not want that your private data can be seen | ||
320 | in the public calendar of your company. | ||
321 | Well, set the property to "private" for all your private data | ||
322 | and specify an outgoing filter: Only " public" and "confidential". | ||
323 | Then you can sync your personal calendar with the calendar of the company, | ||
324 | but your private data is not added to the public calendar. | ||
325 | 279 | ||
326 | ************************************************************************* | 280 | ************************************************************************* |
327 | 6) Details about sync profile kinds | 281 | 6) Details about sync profile kinds |
328 | ************************************************************************* | 282 | ************************************************************************* |
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 | |||
@@ -29,15 +29,16 @@ B) Useful features, that are not straighforward to see | |||
29 | 29 | ||
30 | ****************************************************** | 30 | ****************************************************** |
31 | A) General features | 31 | A) General features |
32 | ****************************************************** | 32 | ****************************************************** |
33 | Features of KO/Pi 1.9.12: | 33 | Features of KO/Pi 2.0.8: |
34 | 0) | 34 | 0) |
35 | Main features: | 35 | Main features: |
36 | KO/Pi makes synchronizing your data easy! | 36 | KO/Pi makes synchronizing your data easy! |
37 | Details in 1) and the sync HowTos. | 37 | Details in 1) and the sync HowTos. |
38 | With KO/Pi you can manage your events/todos/journals. | 38 | With KO/Pi you can manage your events/todos/journals. |
39 | Todos may have subtodos. | 39 | Todos may have subtodos. |
40 | Todos may recur ( details: B)8) Recurring todos) | ||
40 | A subtodo can be changed to a parent root todo. | 41 | A subtodo can be changed to a parent root todo. |
41 | A (sub)todo can be reparented to make it a subtodo of another todo. | 42 | A (sub)todo can be reparented to make it a subtodo of another todo. |
42 | KO/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. | 43 | KO/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. |
43 | KO/Pi is Qt-only based and runs on Sharp Zaurus PDA, Linux and Windows. | 44 | KO/Pi is Qt-only based and runs on Sharp Zaurus PDA, Linux and Windows. |