| -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,12 +1,7 @@ Multi Sync HowTo -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. +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. -In this HowTo we will give an explicit example what to set up -and how configure. +In this HowTo we will give an explicit example what to set up and how configure. We 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. The Zaurus is connected to the Linux Desktop via USB cable. -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. +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. -First we have to install the needed programs, -then we have to configure the programs. +First we have to install the needed programs, then we have to configure the programs. ***************************************** @@ -42,5 +34,5 @@ where you can read how to install. Download file kdepim_X.X.X_for_Windows.exe.zip (b) Installing KDE-Pim/Pi on the Linux laptop and desktop: - Download file KDE-Pim-Pi-1.9.10-SuSE9.1.i586.rpm.zip + Download file KDE-Pim-Pi-2.0.8-SuSE_9.2.i586.rpm.zip (c) Installing KDE-Pim/Pi on the Sharp Zaurus PDA: Depending on your Rom: @@ -60,12 +52,7 @@ available in the help menu of KO/Pi and KA/Pi. ***************************************** -In mutiple sync, we have one aktive sync device and many -other passive sync devices. +In mutiple sync, we have one aktive sync device and many other passive sync devices. -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. +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. We 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 @@ WARNING: -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. +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. -In other words: Please make sure, that the clocks of the devices -you want to sync have only a difference of some seconds! +In other words: Please make sure, that the clocks of the devices you want to sync have only a difference of some seconds! @@ -24,11 +20,12 @@ CONTENT: Note: -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". +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". Details about that in 6) b). -In KDE-Pim/Pi you can synchronize ( sync ) your calendar/addressbook/ -passwordfile with another calendar/addressbook/passwordfile, -by syncing your (local) calendar/addressbook/passwordfile +In KDE-Pim/Pi you can synchronize ( sync ) your +calendar/addressbook/passwordfile with another c +alendar/addressbook/passwordfile, +by syncing your (local) +calendar/addressbook/passwordfile with a (remote) file. This remote file may on your local filesystem @@ -56,13 +53,9 @@ Everything is explained in more details below. NOTE: -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. +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. (Note: KO/Pi(KA/Pi, PWM/Pi) running on Zaurus with FastLoad enabled will never be closed!) -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). -After merging (just a syncing with the changed file) -you will get the new data showing in remote KO/Pi. +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). +After merging (just a syncing with the changed file) you will get the new data showing in remote KO/Pi. ************************************************************************* @@ -206,38 +199,15 @@ k) Profile kind: The same mentioned for calendars is valid for addressbooks as well. -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. - -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. - -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. +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. + +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. + +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. But when was the last synchronization between two calendars? -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. +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. -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. +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. @@ -246,10 +216,8 @@ are deleted on the other as well. ************************************************************************* -Two items are "in conflict", if they have the same unique ID -and they both are modified after the last synchronization. +Two items are "in conflict", if they have the same unique ID and they both are modified after the last synchronization. (Details -> 3) ). -If an item is not modified after the last sync and -it is not found in the other calendar, it is deleted. +If an item is not modified after the last sync and it is not found in the other calendar, it is deleted. On the first sync, there is no item deleted. @@ -294,6 +262,5 @@ SYNC PREFERENCES: ************************************************************************* -A filter is a rule to decide if a particular item -(calendar iten item or contact item) belongs to a set of items. +A filter is a rule to decide if a particular item (calendar iten item or contact item) belongs to a set of items. For example, you can specify a set as: Only items, that belongs to that category. @@ -301,26 +268,13 @@ Or: Only items, that does not belong to that category. Or: Only items, that are public. -If you specify a filter in a syncing profile, you can set the -rules of adding items to the local or remote database. +If you specify a filter in a syncing profile, you can set the rules of adding items to the local or remote database. Example: -You have a public calendar in your company, which contains all -company relevant data. - -You have different projects in the company and for project specific events -is always set the project name as a category: -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. - -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. +You have a public calendar in your company, which contains all company relevant data. + +You have different projects in the company and for project specific events is always set the project name as a category: +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. + +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. ************************************************************************* 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 A) General features ****************************************************** -Features of KO/Pi 1.9.12: +Features of KO/Pi 2.0.8: 0) Main features: @@ -38,4 +38,5 @@ Details in 1) and the sync HowTos. With KO/Pi you can manage your events/todos/journals. Todos may have subtodos. +Todos may recur ( details: B)8) Recurring todos) A subtodo can be changed to a parent root todo. A (sub)todo can be reparented to make it a subtodo of another todo. |