summaryrefslogtreecommitdiffabout
path: root/bin
authorzautrix <zautrix>2005-02-16 19:52:35 (UTC)
committer zautrix <zautrix>2005-02-16 19:52:35 (UTC)
commitebd0c1a894113262ff7c8ecc78261583b68e0907 (patch) (unidiff)
tree67403bfc439aae4a8bd47b1a0ec45b2569191b12 /bin
parentbb5f02a73778bf4623294390a31f1fb92aa95ff5 (diff)
downloadkdepimpi-ebd0c1a894113262ff7c8ecc78261583b68e0907.zip
kdepimpi-ebd0c1a894113262ff7c8ecc78261583b68e0907.tar.gz
kdepimpi-ebd0c1a894113262ff7c8ecc78261583b68e0907.tar.bz2
fixxx
Diffstat (limited to 'bin') (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,12 +1,7 @@
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:
@@ -22,10 +17,7 @@ NOTE: Your KDE version must be 3.3.0 or higher for sncing with.
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*****************************************
@@ -42,5 +34,5 @@ where you can read how to install.
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:
@@ -60,12 +52,7 @@ available in the help menu of KO/Pi and KA/Pi.
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:
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,10 +1,6 @@
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
@@ -24,11 +20,12 @@ CONTENT:
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
@@ -56,13 +53,9 @@ Everything 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*************************************************************************
@@ -206,38 +199,15 @@ k) Profile kind:
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
@@ -246,10 +216,8 @@ are deleted on the other as well.
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.
@@ -294,6 +262,5 @@ SYNC PREFERENCES:
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.
@@ -301,26 +268,13 @@ Or: 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*************************************************************************
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
@@ -31,5 +31,5 @@ B) Useful features, that are not straighforward to see
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:
@@ -38,4 +38,5 @@ Details 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.