author | zautrix <zautrix> | 2005-01-05 18:00:42 (UTC) |
---|---|---|
committer | zautrix <zautrix> | 2005-01-05 18:00:42 (UTC) |
commit | 9bbe06c6cbf70ab8741acc6b356890c072b103e8 (patch) (unidiff) | |
tree | 89ce922f849540b959c6f778c9371f9ff01decf6 /bin | |
parent | 71017beb975666a0f654898ed6a40a5303d567dc (diff) | |
download | kdepimpi-9bbe06c6cbf70ab8741acc6b356890c072b103e8.zip kdepimpi-9bbe06c6cbf70ab8741acc6b356890c072b103e8.tar.gz kdepimpi-9bbe06c6cbf70ab8741acc6b356890c072b103e8.tar.bz2 |
some fixes
-rw-r--r-- | bin/kdepim/SyncHowto.txt | 2 | ||||
-rw-r--r-- | bin/kdepim/WhatsNew.txt | 10 |
2 files changed, 10 insertions, 2 deletions
diff --git a/bin/kdepim/SyncHowto.txt b/bin/kdepim/SyncHowto.txt index 5874fc3..6c1da16 100644 --- a/bin/kdepim/SyncHowto.txt +++ b/bin/kdepim/SyncHowto.txt | |||
@@ -1,258 +1,258 @@ | |||
1 | WARNING: | 1 | WARNING: |
2 | YOU MAY GET UNEXSPECTED (I.E. WRONG) SYNCHRONIZATION RESULTS, | 2 | YOU MAY GET UNEXPECTED (I.E. WRONG) SYNCHRONIZATION RESULTS, |
3 | IF YOU CHANGE AN EVENT ON THE FIRST DEVICE AND SYNC IMMEDIATELY FROM | 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 | 4 | THE OTHER DEVICE WITH THIS DEVICE, IF THE CLOCKS OF THE TWO DEVICES |
5 | HAVE TOO MUCH DIFFERENCE. | 5 | HAVE TOO MUCH DIFFERENCE. |
6 | 6 | ||
7 | In other words: Please make sure, that the clocks of the devices | 7 | In other words: Please make sure, that the clocks of the devices |
8 | you want to sync have only a difference of some seconds! | 8 | you want to sync have only a difference of some seconds! |
9 | 9 | ||
10 | 10 | ||
11 | CONTENT: | 11 | CONTENT: |
12 | 12 | ||
13 | 0) How syncing works | 13 | 0) How syncing works |
14 | 1) Qick overview of settings | 14 | 1) Qick overview of settings |
15 | 2) Sync settings in sync dialog | 15 | 2) Sync settings in sync dialog |
16 | 3) Syncing background | 16 | 3) Syncing background |
17 | 4) Sync preferences | 17 | 4) Sync preferences |
18 | 5) Details about sync profile kinds | 18 | 5) Details about sync profile kinds |
19 | 19 | ||
20 | ************************************************************************* | 20 | ************************************************************************* |
21 | 0) How syncing works | 21 | 0) How syncing works |
22 | ************************************************************************* | 22 | ************************************************************************* |
23 | 23 | ||
24 | Note: | 24 | Note: |
25 | The recommended and easiest way to syncronize two devices where | 25 | The recommended and easiest way to syncronize two devices where |
26 | KO/Pi, KA/Pi or PWM/Pi is installed, is the profile kind "Pi-Sync". | 26 | KO/Pi, KA/Pi or PWM/Pi is installed, is the profile kind "Pi-Sync". |
27 | Details about that in 5) b). | 27 | Details about that in 5) b). |
28 | 28 | ||
29 | In KDE-Pim/Pi you can synchronize ( sync ) your calendar/addressbook/ | 29 | In KDE-Pim/Pi you can synchronize ( sync ) your calendar/addressbook/ |
30 | passwordfile with another calendar/addressbook/passwordfile, | 30 | passwordfile with another calendar/addressbook/passwordfile, |
31 | by syncing your (local) calendar/addressbook/passwordfile | 31 | by syncing your (local) calendar/addressbook/passwordfile |
32 | with a (remote) file. | 32 | with a (remote) file. |
33 | This remote file may on your local filesystem | 33 | This remote file may on your local filesystem |
34 | or on another (remote) device. | 34 | or on another (remote) device. |
35 | 35 | ||
36 | If you want to sync with another remote device, you have to create | 36 | If you want to sync with another remote device, you have to create |
37 | a sync profile. | 37 | a sync profile. |
38 | You have two choices for choosing the profil kind: | 38 | You have two choices for choosing the profil kind: |
39 | I) You can choose profile kind "Remote file" and specify a | 39 | I) You can choose profile kind "Remote file" and specify a |
40 | command line download/upload command ( like scp, ftp, ...) to | 40 | command line download/upload command ( like scp, ftp, ...) to |
41 | a) download the remote file to your local machine to a temp file | 41 | a) download the remote file to your local machine to a temp file |
42 | b) sync with this temp file | 42 | b) sync with this temp file |
43 | c) upload the synced file to the remote device | 43 | c) upload the synced file to the remote device |
44 | II) If you want to sync with a device, where KO/Pi( or KA/Pi, PWM/Pi) is | 44 | II) If you want to sync with a device, where KO/Pi( or KA/Pi, PWM/Pi) is |
45 | installed, you can easily get the remote file via network | 45 | installed, you can easily get the remote file via network |
46 | with the build in file transfer feature: | 46 | with the build in file transfer feature: |
47 | Choose profile kind "Pi-Sync" and | 47 | Choose profile kind "Pi-Sync" and |
48 | a) Start KO/Pi,KA/Pi or PWM/Pi on remote device and | 48 | a) Start KO/Pi,KA/Pi or PWM/Pi on remote device and |
49 | enable "Pi-Sync" on remote device with password and port. | 49 | enable "Pi-Sync" on remote device with password and port. |
50 | b) Specify password, port and IP address in your profile. | 50 | b) Specify password, port and IP address in your profile. |
51 | 51 | ||
52 | 52 | ||
53 | You can sync with your mobile phone as well. | 53 | You can sync with your mobile phone as well. |
54 | Everything is explained in more details below. | 54 | Everything is explained in more details below. |
55 | 55 | ||
56 | NOTE: | 56 | NOTE: |
57 | If you do not use profile kind "Pi-Sync", | 57 | If you do not use profile kind "Pi-Sync", |
58 | it is recommended to close | 58 | it is recommended to close |
59 | a running KO/Pi (KA/Pi, PWM/Pi) on the remote device. | 59 | a running KO/Pi (KA/Pi, PWM/Pi) on the remote device. |
60 | (Note: KO/Pi(KA/Pi, PWM/Pi) running on Zaurus with | 60 | (Note: KO/Pi(KA/Pi, PWM/Pi) running on Zaurus with |
61 | FastLoad enabled will never be closed!) | 61 | FastLoad enabled will never be closed!) |
62 | After syncing with a running KO/Pi on the remote device, | 62 | After syncing with a running KO/Pi on the remote device, |
63 | a "save" on the remote device will tell you that it needs to merge (sync). | 63 | a "save" on the remote device will tell you that it needs to merge (sync). |
64 | After merging (just a syncing with the changed file) | 64 | After merging (just a syncing with the changed file) |
65 | you will get the new data showing in remote KO/Pi. | 65 | you will get the new data showing in remote KO/Pi. |
66 | 66 | ||
67 | ************************************************************************* | 67 | ************************************************************************* |
68 | 1) Qick overview of settings | 68 | 1) Qick overview of settings |
69 | ************************************************************************* | 69 | ************************************************************************* |
70 | 70 | ||
71 | a) Open sync settings dialog (Menu Synchronize - Configure...) | 71 | a) Open sync settings dialog (Menu Synchronize - Configure...) |
72 | b) Give your device a unique name. | 72 | b) Give your device a unique name. |
73 | (unique in the set of all devices you want to sync with). | 73 | (unique in the set of all devices you want to sync with). |
74 | If you have already configured another devive and created | 74 | If you have already configured another devive and created |
75 | there a sync profile to sync with this device, give your device | 75 | there a sync profile to sync with this device, give your device |
76 | the same name as this sync profile! The same name is important, | 76 | the same name as this sync profile! The same name is important, |
77 | because it makes it possible to sync first A->B | 77 | because it makes it possible to sync first A->B |
78 | (A local device, that performs the sync, B remote device) | 78 | (A local device, that performs the sync, B remote device) |
79 | and then B->A. Such that the B->A sync knows about the | 79 | and then B->A. Such that the B->A sync knows about the |
80 | already performed A->B sync. | 80 | already performed A->B sync. |
81 | That means: It is unimportant if you sync A->B or B->A, | 81 | That means: It is unimportant if you sync A->B or B->A, |
82 | the devices A and B will be synced properly. | 82 | the devices A and B will be synced properly. |
83 | c) Create a new sync profile and give it a unique name. | 83 | c) Create a new sync profile and give it a unique name. |
84 | (unique in the set of all sync profiles on this device). | 84 | (unique in the set of all sync profiles on this device). |
85 | If you want to sync with a device, where KO/Pi is already installed | 85 | If you want to sync with a device, where KO/Pi is already installed |
86 | and which has a given unique device name, use this device name as | 86 | and which has a given unique device name, use this device name as |
87 | your profile name ( refer to b) ). | 87 | your profile name ( refer to b) ). |
88 | d) Coose the profile kind of your syncing method: | 88 | d) Coose the profile kind of your syncing method: |
89 | (i) Local file or | 89 | (i) Local file or |
90 | (ii) Pi-Sync or | 90 | (ii) Pi-Sync or |
91 | (iii) Remote file or | 91 | (iii) Remote file or |
92 | (iiii) Mobile Phone. | 92 | (iiii) Mobile Phone. |
93 | Detailed explanation in 5) | 93 | Detailed explanation in 5) |
94 | e) Choose the other profile options. | 94 | e) Choose the other profile options. |
95 | Detailed explanation in 2) | 95 | Detailed explanation in 2) |
96 | f) Close sync dialog with OK. | 96 | f) Close sync dialog with OK. |
97 | g) Sync. | 97 | g) Sync. |
98 | 98 | ||
99 | NOTE: | 99 | NOTE: |
100 | AFTER SYNCING THERE ARE "SYNC EVENTS" CREATED | 100 | AFTER SYNCING THERE ARE "SYNC EVENTS" CREATED |
101 | (OR UPDATED, IF IT ALREADY EXITS) FOR EACH SYNC PROFILE. | 101 | (OR UPDATED, IF IT ALREADY EXITS) FOR EACH SYNC PROFILE. |
102 | YOU MAY NOT DELETE OR CHANGE THESE EVENTS. | 102 | YOU MAY NOT DELETE OR CHANGE THESE EVENTS. |
103 | 103 | ||
104 | ************************************************************************* | 104 | ************************************************************************* |
105 | 2) Sync settings in sync dialog | 105 | 2) Sync settings in sync dialog |
106 | ************************************************************************* | 106 | ************************************************************************* |
107 | 107 | ||
108 | a) Local device name: | 108 | a) Local device name: |
109 | -> 1) b) | 109 | -> 1) b) |
110 | b) Profile: | 110 | b) Profile: |
111 | -> 1) c) | 111 | -> 1) c) |
112 | c) Include in multiple sync: | 112 | c) Include in multiple sync: |
113 | In the Synchronize menu, there is a multiple sync menu entry. | 113 | In the Synchronize menu, there is a multiple sync menu entry. |
114 | If you choose this menu entry, all user defined profiles with this | 114 | If you choose this menu entry, all user defined profiles with this |
115 | 'Include in multiple sync' option enabled will be synced | 115 | 'Include in multiple sync' option enabled will be synced |
116 | one after another. And this twice. This will take some time. | 116 | one after another. And this twice. This will take some time. |
117 | After that sync, on all devices should be the same data. | 117 | After that sync, on all devices should be the same data. |
118 | d) Ask for preferences before sync: | 118 | d) Ask for preferences before sync: |
119 | Check this to be asked for sync preferences settings before each sync. | 119 | Check this to be asked for sync preferences settings before each sync. |
120 | If the profile kind is "Pi-Sync" you will be asked to confirm | 120 | If the profile kind is "Pi-Sync" you will be asked to confirm |
121 | the "Pi-Sync" specific settings (Password,IP address, port number) | 121 | the "Pi-Sync" specific settings (Password,IP address, port number) |
122 | as well. That makes it possible to use that profile for a | 122 | as well. That makes it possible to use that profile for a |
123 | device that is connected via DHCP to the network and gets different | 123 | device that is connected via DHCP to the network and gets different |
124 | IP addresses when connection to the network. | 124 | IP addresses when connection to the network. |
125 | e) Sync preferences: | 125 | e) Sync preferences: |
126 | Choose here your sync preferences. | 126 | Choose here your sync preferences. |
127 | Details -> 4) | 127 | Details -> 4) |
128 | f) Show summary after sync: | 128 | f) Show summary after sync: |
129 | Check this to get a small summary dialog after sync | 129 | Check this to get a small summary dialog after sync |
130 | about number of added/changed/deleted events on local/remote. | 130 | about number of added/changed/deleted events on local/remote. |
131 | g) Write back synced data: | 131 | g) Write back synced data: |
132 | Uncheck this to update the local calendar only. | 132 | Uncheck this to update the local calendar only. |
133 | I.e. your local calendar is synced with the remote calendar | 133 | I.e. your local calendar is synced with the remote calendar |
134 | but nothing on the remote calendar is changed. | 134 | but nothing on the remote calendar is changed. |
135 | If you uncheck "Write back synced data", the settings | 135 | If you uncheck "Write back synced data", the settings |
136 | under h) and i) are ignored, of course. | 136 | under h) and i) are ignored, of course. |
137 | h) --Write back (on remote) existing entries only: | 137 | h) --Write back (on remote) existing entries only: |
138 | Check this to update the remote data only. | 138 | Check this to update the remote data only. |
139 | I.e. no data from yor local calendar/addressbook is added to the | 139 | I.e. no data from yor local calendar/addressbook is added to the |
140 | remote device. You may use this option to | 140 | remote device. You may use this option to |
141 | sync against some kind of "public calendar/addressbook" without | 141 | sync against some kind of "public calendar/addressbook" without |
142 | writing back your personal data. | 142 | writing back your personal data. |
143 | i) --Write back (calendar) entries in future only: | 143 | i) --Write back (calendar) entries in future only: |
144 | Check this to write back only calendar entries in future. | 144 | Check this to write back only calendar entries in future. |
145 | (Useful when syncing with mobile phones.) | 145 | (Useful when syncing with mobile phones.) |
146 | You can specify the date range in weeks with | 146 | You can specify the date range in weeks with |
147 | ---- Max. weeks in future. | 147 | ---- Max. weeks in future. |
148 | Note: The date range starts always 7 days before the actual date! | 148 | Note: The date range starts always 7 days before the actual date! |
149 | I.e. the calendar events of the last week are written back always. | 149 | I.e. the calendar events of the last week are written back always. |
150 | j) Profile kind: | 150 | j) Profile kind: |
151 | Details -> 5) | 151 | Details -> 5) |
152 | 152 | ||
153 | ************************************************************************* | 153 | ************************************************************************* |
154 | 3) Syncing background | 154 | 3) Syncing background |
155 | ************************************************************************* | 155 | ************************************************************************* |
156 | 156 | ||
157 | The same mentioned for calendars is valid for addressbooks as well. | 157 | The same mentioned for calendars is valid for addressbooks as well. |
158 | 158 | ||
159 | Synchronizing calendars ( i.e. files ) means, | 159 | Synchronizing calendars ( i.e. files ) means, |
160 | to merge two calendars in a useful way. | 160 | to merge two calendars in a useful way. |
161 | If the two calendars are completely different, | 161 | If the two calendars are completely different, |
162 | there is no problem, the resulting calendar contains | 162 | there is no problem, the resulting calendar contains |
163 | all data from the local and from the remote calendar. | 163 | all data from the local and from the remote calendar. |
164 | 164 | ||
165 | Problems will occur, if you have edited items | 165 | Problems will occur, if you have edited items |
166 | from the local calendar on the remote machine. | 166 | from the local calendar on the remote machine. |
167 | Then it could be, that items are in conflict. | 167 | Then it could be, that items are in conflict. |
168 | Two items are "in conflict", if they have the | 168 | Two items are "in conflict", if they have the |
169 | same unique ID (which get an item at time of | 169 | same unique ID (which get an item at time of |
170 | creation and owns it until it is deleted ) | 170 | creation and owns it until it is deleted ) |
171 | and they both are modified after the last | 171 | and they both are modified after the last |
172 | synchronization. | 172 | synchronization. |
173 | 173 | ||
174 | At first sync of two calendars there is no item deleted. | 174 | At first sync of two calendars there is no item deleted. |
175 | If the calendars are synced before and there is an item, | 175 | If the calendars are synced before and there is an item, |
176 | which is not edited after the last sync and is only | 176 | which is not edited after the last sync and is only |
177 | available in one calendar, then this item is deleted | 177 | available in one calendar, then this item is deleted |
178 | in this calendar. | 178 | in this calendar. |
179 | 179 | ||
180 | But when was the last synchronization between two calendars? | 180 | But when was the last synchronization between two calendars? |
181 | 181 | ||
182 | To know that, KO/Pi creates at first syncing | 182 | To know that, KO/Pi creates at first syncing |
183 | of two files an unique event "<profile name> - sync Event" | 183 | of two files an unique event "<profile name> - sync Event" |
184 | on the remote and the local calendar. | 184 | on the remote and the local calendar. |
185 | After syncing, the start time of this event is set | 185 | After syncing, the start time of this event is set |
186 | to the time of syncing. | 186 | to the time of syncing. |
187 | The event is read only and the user may not change it. | 187 | The event is read only and the user may not change it. |
188 | 188 | ||
189 | If two such files are synced, that both have an event | 189 | If two such files are synced, that both have an event |
190 | "<profile name> - sync Event" and the events have | 190 | "<profile name> - sync Event" and the events have |
191 | the same start time, then deleted items on the one calendar | 191 | the same start time, then deleted items on the one calendar |
192 | are deleted on the other as well. | 192 | are deleted on the other as well. |
193 | 193 | ||
194 | 194 | ||
195 | ************************************************************************* | 195 | ************************************************************************* |
196 | 4) Sync preferences | 196 | 4) Sync preferences |
197 | ************************************************************************* | 197 | ************************************************************************* |
198 | 198 | ||
199 | Two items are "in conflict", if they have the same unique ID | 199 | Two items are "in conflict", if they have the same unique ID |
200 | and they both are modified after the last synchronization. | 200 | and they both are modified after the last synchronization. |
201 | (Details -> 3) ). | 201 | (Details -> 3) ). |
202 | 202 | ||
203 | If an item is not modified after the last sync and | 203 | If an item is not modified after the last sync and |
204 | it is not found in the other calendar, it is deleted. | 204 | it is not found in the other calendar, it is deleted. |
205 | 205 | ||
206 | On the first sync, there is no item deleted. | 206 | On the first sync, there is no item deleted. |
207 | 207 | ||
208 | SYNC PREFERENCES: | 208 | SYNC PREFERENCES: |
209 | -Take local entry on conflict: | 209 | -Take local entry on conflict: |
210 | Takes the local entry on conflict. | 210 | Takes the local entry on conflict. |
211 | If it is the first sync, | 211 | If it is the first sync, |
212 | "Ask for every entry" | 212 | "Ask for every entry" |
213 | is chosen automatically, | 213 | is chosen automatically, |
214 | if this is selected. | 214 | if this is selected. |
215 | 215 | ||
216 | -Take remote entry on conflict: | 216 | -Take remote entry on conflict: |
217 | Takes the remote entry on conflict. | 217 | Takes the remote entry on conflict. |
218 | If it is the first sync, | 218 | If it is the first sync, |
219 | "Ask for every entry" | 219 | "Ask for every entry" |
220 | is chosen automatically, | 220 | is chosen automatically, |
221 | if this is selected. | 221 | if this is selected. |
222 | 222 | ||
223 | -Take newest entry on conflict: | 223 | -Take newest entry on conflict: |
224 | This takes the newest entry on conflict. | 224 | This takes the newest entry on conflict. |
225 | May be the most useful syncing mode. | 225 | May be the most useful syncing mode. |
226 | 226 | ||
227 | -Ask for every entry on conflict: | 227 | -Ask for every entry on conflict: |
228 | Pops up an event viewer dialog and | 228 | Pops up an event viewer dialog and |
229 | shows the two conflicting entries there. | 229 | shows the two conflicting entries there. |
230 | The user can chose, which entry he would like to take. | 230 | The user can chose, which entry he would like to take. |
231 | The button for the newest entry | 231 | The button for the newest entry |
232 | is automatically set as default button. | 232 | is automatically set as default button. |
233 | The color for the newest entry is green. | 233 | The color for the newest entry is green. |
234 | 234 | ||
235 | -Force: Take local entry always: | 235 | -Force: Take local entry always: |
236 | Even if the calendars are already synced | 236 | Even if the calendars are already synced |
237 | there is no item deleted on local. | 237 | there is no item deleted on local. |
238 | 238 | ||
239 | -Force: Take remote entry always: | 239 | -Force: Take remote entry always: |
240 | Analogous to | 240 | Analogous to |
241 | "Force: Take local entry always" | 241 | "Force: Take local entry always" |
242 | 242 | ||
243 | ************************************************************************* | 243 | ************************************************************************* |
244 | 5) Details about sync profile kinds | 244 | 5) Details about sync profile kinds |
245 | ************************************************************************* | 245 | ************************************************************************* |
246 | 246 | ||
247 | a) Local file | 247 | a) Local file |
248 | Please specify a local file you want to sync with. | 248 | Please specify a local file you want to sync with. |
249 | Note: If you are syncing a file, which is used by KA/Pi, please check the | 249 | Note: If you are syncing a file, which is used by KA/Pi, please check the |
250 | "Addressbook file (*.vcf) is used by KA/Pi". | 250 | "Addressbook file (*.vcf) is used by KA/Pi". |
251 | If you are syncing with a file from KAddressbook or another program, | 251 | If you are syncing with a file from KAddressbook or another program, |
252 | please uncheck "Addressbook file (*.vcf) is used by KA/Pi". | 252 | please uncheck "Addressbook file (*.vcf) is used by KA/Pi". |
253 | To set this properly is important! KA/Pi uses a "last modified" property, | 253 | To set this properly is important! KA/Pi uses a "last modified" property, |
254 | which is not supported by KAddressbook. | 254 | which is not supported by KAddressbook. |
255 | 255 | ||
256 | b) Pi-Sync (direct Kx/Pi to Kx/Pi sync) | 256 | b) Pi-Sync (direct Kx/Pi to Kx/Pi sync) |
257 | We mention here only KO/Pi, but the same is valid for KA/Pi. | 257 | We mention here only KO/Pi, but the same is valid for KA/Pi. |
258 | If you want to sync with a device, where KO/Pi is | 258 | If you want to sync with a device, where KO/Pi is |
diff --git a/bin/kdepim/WhatsNew.txt b/bin/kdepim/WhatsNew.txt index 1a8b885..df0b2eb 100644 --- a/bin/kdepim/WhatsNew.txt +++ b/bin/kdepim/WhatsNew.txt | |||
@@ -1,286 +1,294 @@ | |||
1 | Info about the changes in new versions of KDE-Pim/Pi | 1 | Info about the changes in new versions of KDE-Pim/Pi |
2 | 2 | ||
3 | ********** VERSION 1.9.16 ************ | 3 | ********** VERSION 1.9.16 ************ |
4 | 4 | ||
5 | KO/Pi: | 5 | KO/Pi: |
6 | Fixed search dialog size on Z 6000 (480x640 display). | 6 | Fixed search dialog size on Z 6000 (480x640 display). |
7 | Added setting to hide/show time in agenda items. | 7 | Added setting to hide/show time in agenda items. |
8 | Added setting to hide not running todos in todo view. | 8 | Added setting to hide not running todos in todo view. |
9 | Added columns for start date/time in todo view. | 9 | Added columns for start date/time in todo view. |
10 | Replaced the solid half-hour lines in agenda view by dot lines. | 10 | Replaced the solid half-hour lines in agenda view by dot lines. |
11 | Fixed some minor problems. (Like word wrap in help text windows). | ||
12 | |||
13 | Fixed a strange problem in KO/Pi alarm applet. | ||
14 | Did not find the actual problem, | ||
15 | such that now Qtopia reboots if deinstalling the alarm applet. | ||
16 | But the alarm applet should work again. | ||
17 | |||
11 | 18 | ||
12 | ********** VERSION 1.9.15 ************ | 19 | ********** VERSION 1.9.15 ************ |
13 | 20 | ||
14 | Usebilty enhancements in KO/Pi: | 21 | Usebilty enhancements in KO/Pi: |
15 | When clicking on the date in a month view cell, the day view is shown. | 22 | When clicking on the date in a month view cell, the day view is shown. |
16 | Old behaviour was, that the "new event" dialog popped up. | 23 | Old behaviour was, that the "new event" dialog popped up. |
17 | 24 | ||
18 | Added a one step "undo delete" in KO/Pi (Accessable in the "Action" menu). | 25 | Added a one step "undo delete" in KO/Pi (Accessable in the "Action" menu). |
19 | That means, you can restore the latest | 26 | That means, you can restore the latest |
20 | event/todo/journal you have deleted. | 27 | event/todo/journal you have deleted. |
21 | A journal is deleted, if you clear all the text of the journal. | 28 | A journal is deleted, if you clear all the text of the journal. |
22 | 29 | ||
23 | Fixed the bug of the editor dialogs in KO/Pi of version 1.9.14. | 30 | Fixed the bug of the editor dialogs in KO/Pi of version 1.9.14. |
24 | 31 | ||
25 | KA/Pi starting in 480x640 resolution: | 32 | KA/Pi starting in 480x640 resolution: |
26 | Hide the filter action in toolbar | 33 | Hide the filter action in toolbar |
27 | and added icons for undo/delete/redo in toolbar. | 34 | and added icons for undo/delete/redo in toolbar. |
28 | 35 | ||
29 | Change in OM/Pi ViewMail dialog: | 36 | Change in OM/Pi ViewMail dialog: |
30 | When clicking on the "delete" icon the mail is deleted after confirmation as usual. But the edit dialog is not closed as before, now the next mail in the folder is shown automatically (if there is any). | 37 | When clicking on the "delete" icon the mail is deleted after confirmation as usual. |
38 | But the edit dialog is not closed as before, now the next mail in the folder is shown automatically (if there is any). | ||
31 | 39 | ||
32 | Fixed a crash when deleting mail-accounts in OM/Pi. | 40 | Fixed a crash when deleting mail-accounts in OM/Pi. |
33 | 41 | ||
34 | 42 | ||
35 | ********** VERSION 1.9.14 ************ | 43 | ********** VERSION 1.9.14 ************ |
36 | 44 | ||
37 | Fixed some problems with the dialog sizes when switching | 45 | Fixed some problems with the dialog sizes when switching |
38 | portrait/landscape mode on 640x480 PDA display. | 46 | portrait/landscape mode on 640x480 PDA display. |
39 | 47 | ||
40 | Fixed some other small bugs in KA/Pi KO/Pi and OM/Pi and PwM/Pi. | 48 | Fixed some other small bugs in KA/Pi KO/Pi and OM/Pi and PwM/Pi. |
41 | 49 | ||
42 | Fixed an ugly bug in KOpieMail: | 50 | Fixed an ugly bug in KOpieMail: |
43 | KOpieMail was not able to write files (mails) to MSDOS file system, | 51 | KOpieMail was not able to write files (mails) to MSDOS file system, |
44 | like on an usual preformatted SD card. That should work now. | 52 | like on an usual preformatted SD card. That should work now. |
45 | To save your mail data on the Sd card do the following: | 53 | To save your mail data on the Sd card do the following: |
46 | Create a dir on the SD card: | 54 | Create a dir on the SD card: |
47 | mkdir /mnt/card/localmail | 55 | mkdir /mnt/card/localmail |
48 | Go to your home dir: | 56 | Go to your home dir: |
49 | cd | 57 | cd |
50 | Go to kopiemail data storage dir: | 58 | Go to kopiemail data storage dir: |
51 | cd kdepim/apps/kopiemail | 59 | cd kdepim/apps/kopiemail |
52 | Create a symlink to the SD card: | 60 | Create a symlink to the SD card: |
53 | ls -s /mnt/card/localmail | 61 | ls -s /mnt/card/localmail |
54 | Now KOpieMail will store all mails on the SD card. | 62 | Now KOpieMail will store all mails on the SD card. |
55 | 63 | ||
56 | KO/Pi Monthview: | 64 | KO/Pi Monthview: |
57 | Now "Go to Today" selects the current month from day 1-end, | 65 | Now "Go to Today" selects the current month from day 1-end, |
58 | not the current date + some days. | 66 | not the current date + some days. |
59 | I.e. "Go to Today" shows now always | 67 | I.e. "Go to Today" shows now always |
60 | the current month with first day of month in the first row. | 68 | the current month with first day of month in the first row. |
61 | 69 | ||
62 | Added missing German translation. | 70 | Added missing German translation. |
63 | 71 | ||
64 | Fixed icons of executeable on Wintendo. | 72 | Fixed icons of executeable on Wintendo. |
65 | 73 | ||
66 | Added a "Show next Mail" button to the OM/Pi | 74 | Added a "Show next Mail" button to the OM/Pi |
67 | mail viewer such that the mail below the current mail | 75 | mail viewer such that the mail below the current mail |
68 | in the mail list view of the current folder | 76 | in the mail list view of the current folder |
69 | can be read with a single click. | 77 | can be read with a single click. |
70 | 78 | ||
71 | 79 | ||
72 | ********** VERSION 1.9.13 ************ | 80 | ********** VERSION 1.9.13 ************ |
73 | 81 | ||
74 | Fixed nasty PwM/Pi file reading bug, when | 82 | Fixed nasty PwM/Pi file reading bug, when |
75 | the used hash algo of file is different then the global | 83 | the used hash algo of file is different then the global |
76 | hash algo. | 84 | hash algo. |
77 | 85 | ||
78 | Added KA/Pi support for opie mailit mailapplication. | 86 | Added KA/Pi support for opie mailit mailapplication. |
79 | 87 | ||
80 | Fixed some bugs in OM/Pi. | 88 | Fixed some bugs in OM/Pi. |
81 | Now character conversion tables are available for the Zaurus | 89 | Now character conversion tables are available for the Zaurus |
82 | to make OM/Pi working properly. | 90 | to make OM/Pi working properly. |
83 | To get the character conversion in OM/Pi working, please download | 91 | To get the character conversion in OM/Pi working, please download |
84 | at the sourceforge project site the package | 92 | at the sourceforge project site the package |
85 | sr-character-conversion_SharpROM_arm.ipk.zip | 93 | sr-character-conversion_SharpROM_arm.ipk.zip |
86 | (or oz-character-conversion_OZ-gcc3xx_arm.ipk.zip for OZ roms) | 94 | (or oz-character-conversion_OZ-gcc3xx_arm.ipk.zip for OZ roms) |
87 | from the section "general files for KDE/Pim" | 95 | from the section "general files for KDE/Pim" |
88 | Instructions how to install this package are in a ReadMe in this file. | 96 | Instructions how to install this package are in a ReadMe in this file. |
89 | 97 | ||
90 | 98 | ||
91 | Fixed the orientation change problem in KA/Pi when switching | 99 | Fixed the orientation change problem in KA/Pi when switching |
92 | portrait/landscape mode. | 100 | portrait/landscape mode. |
93 | 101 | ||
94 | French translation available for KA/Pi and OM/Pi. | 102 | French translation available for KA/Pi and OM/Pi. |
95 | 103 | ||
96 | Fixed some problems with categories in KO/Pi in DTM sync. | 104 | Fixed some problems with categories in KO/Pi in DTM sync. |
97 | 105 | ||
98 | Added selection dialog for export to phone in KA/Pi. | 106 | Added selection dialog for export to phone in KA/Pi. |
99 | 107 | ||
100 | If in KO/Pi is an attendee selected to add to a meeting and this | 108 | If in KO/Pi is an attendee selected to add to a meeting and this |
101 | attendee is already in the list of attendees, this person is not added | 109 | attendee is already in the list of attendees, this person is not added |
102 | again. | 110 | again. |
103 | 111 | ||
104 | Some menu cleanup in KA/Pi. | 112 | Some menu cleanup in KA/Pi. |
105 | 113 | ||
106 | ********** VERSION 1.9.12 ************ | 114 | ********** VERSION 1.9.12 ************ |
107 | 115 | ||
108 | Fix for the bug in KO/Pi What's Next view of version 1.9.11. | 116 | Fix for the bug in KO/Pi What's Next view of version 1.9.11. |
109 | 117 | ||
110 | Bugfix: Licence file is now shown again. | 118 | Bugfix: Licence file is now shown again. |
111 | 119 | ||
112 | OM/Pi now supports Unicode (utf8 charset). | 120 | OM/Pi now supports Unicode (utf8 charset). |
113 | Fixed some bugs in OM/Pi. | 121 | Fixed some bugs in OM/Pi. |
114 | 122 | ||
115 | KA/Pi has more German translation. | 123 | KA/Pi has more German translation. |
116 | 124 | ||
117 | 125 | ||
118 | ********** VERSION 1.9.11 ************ | 126 | ********** VERSION 1.9.11 ************ |
119 | 127 | ||
120 | Fixed several problems in PWM/Pi, like | 128 | Fixed several problems in PWM/Pi, like |
121 | asking the user, if unsaved changed are pending | 129 | asking the user, if unsaved changed are pending |
122 | when closing the app. | 130 | when closing the app. |
123 | And PwM/Pi handles now different texts for the | 131 | And PwM/Pi handles now different texts for the |
124 | fields Description, Username, Password, configurable per category. | 132 | fields Description, Username, Password, configurable per category. |
125 | 133 | ||
126 | Fixed a crash in KO/Pi , when importing/loading vcs files | 134 | Fixed a crash in KO/Pi , when importing/loading vcs files |
127 | which have an entry with an attendee with state: | 135 | which have an entry with an attendee with state: |
128 | NEEDS ACTION | 136 | NEEDS ACTION |
129 | 137 | ||
130 | Fixed some problems in the German translation of OM/Pi, | 138 | Fixed some problems in the German translation of OM/Pi, |
131 | which makes some dialogs not fitting on the screen | 139 | which makes some dialogs not fitting on the screen |
132 | of the Z 5500. | 140 | of the Z 5500. |
133 | 141 | ||
134 | Fixed Qtopia crash, when disabling/deinstalling | 142 | Fixed Qtopia crash, when disabling/deinstalling |
135 | KO/Pi alarm applet. | 143 | KO/Pi alarm applet. |
136 | 144 | ||
137 | Implemented direct KDE<->KA/Pi sync for KA/Pi running | 145 | Implemented direct KDE<->KA/Pi sync for KA/Pi running |
138 | on Linux desktop. | 146 | on Linux desktop. |
139 | 147 | ||
140 | Added feature "remove sync info" to sync menu. | 148 | Added feature "remove sync info" to sync menu. |
141 | 149 | ||
142 | Tweaked the KO/Pi What's next view a bit, added | 150 | Tweaked the KO/Pi What's next view a bit, added |
143 | setting to hide events that are done. | 151 | setting to hide events that are done. |
144 | 152 | ||
145 | Disabled "beam receive enabled" on startup to | 153 | Disabled "beam receive enabled" on startup to |
146 | avoid problems if Fastload is enabled. | 154 | avoid problems if Fastload is enabled. |
147 | Please set "beam receive enabled", | 155 | Please set "beam receive enabled", |
148 | if you want to receive data via IR. | 156 | if you want to receive data via IR. |
149 | 157 | ||
150 | Fixed bug in direct KDE<->KO/Pi sync for KO/Pi running | 158 | Fixed bug in direct KDE<->KO/Pi sync for KO/Pi running |
151 | on Linux desktop. | 159 | on Linux desktop. |
152 | 160 | ||
153 | Made in KA/Pi scrolling possible, if details view is selected. | 161 | Made in KA/Pi scrolling possible, if details view is selected. |
154 | (The keyboard focus is set automatically to the search line) | 162 | (The keyboard focus is set automatically to the search line) |
155 | 163 | ||
156 | Fixed a bug in DMT sync, that a new entry in DTM was added | 164 | Fixed a bug in DMT sync, that a new entry in DTM was added |
157 | on every sync to Kx/Pi. | 165 | on every sync to Kx/Pi. |
158 | 166 | ||
159 | Fixed missing writing of KA/Pi categories to DMT entries when syncing. | 167 | Fixed missing writing of KA/Pi categories to DMT entries when syncing. |
160 | 168 | ||
161 | Fixed a bug in DMT sync with todos created in KO/Pi containing | 169 | Fixed a bug in DMT sync with todos created in KO/Pi containing |
162 | non-latin1 characters. | 170 | non-latin1 characters. |
163 | 171 | ||
164 | Rearranged package contents of Sharp-ipks and made all | 172 | Rearranged package contents of Sharp-ipks and made all |
165 | packages installable on SD again. | 173 | packages installable on SD again. |
166 | 174 | ||
167 | Fixed the writing of addressbook data in DTM sync. | 175 | Fixed the writing of addressbook data in DTM sync. |
168 | Empty fields in KA/Pi were not removed. | 176 | Empty fields in KA/Pi were not removed. |
169 | 177 | ||
170 | Added better category handling in KA/Pi: | 178 | Added better category handling in KA/Pi: |
171 | Added item | 179 | Added item |
172 | Edit Categories and | 180 | Edit Categories and |
173 | Manage new categories | 181 | Manage new categories |
174 | to the settings menu. | 182 | to the settings menu. |
175 | Possible to configure a view to display categories. | 183 | Possible to configure a view to display categories. |
176 | 184 | ||
177 | Added detailed "KDE Sync Howto" and "Multi Sync Howto" to Help menu. | 185 | Added detailed "KDE Sync Howto" and "Multi Sync Howto" to Help menu. |
178 | 186 | ||
179 | Fixed displaying of "free" days and time in KO Monthview and Agendaview. | 187 | Fixed displaying of "free" days and time in KO Monthview and Agendaview. |
180 | 188 | ||
181 | ... and many other bugfixes. | 189 | ... and many other bugfixes. |
182 | 190 | ||
183 | ********** VERSION 1.9.10 ************ | 191 | ********** VERSION 1.9.10 ************ |
184 | 192 | ||
185 | Many internal small bugfixes. | 193 | Many internal small bugfixes. |
186 | And fix of the "big" bug in KO/Pi, | 194 | And fix of the "big" bug in KO/Pi, |
187 | that after Syncing the appointments had an offset by several hours. | 195 | that after Syncing the appointments had an offset by several hours. |
188 | That was a problem with the internal timezone setting, | 196 | That was a problem with the internal timezone setting, |
189 | introduced by the changed timezone configuration settings. | 197 | introduced by the changed timezone configuration settings. |
190 | 198 | ||
191 | German translation for OM/Pi is now available. | 199 | German translation for OM/Pi is now available. |
192 | 200 | ||
193 | 201 | ||
194 | ********** VERSION 1.9.9 ************ | 202 | ********** VERSION 1.9.9 ************ |
195 | 203 | ||
196 | KDE-Pim/Pi has a new Member! | 204 | KDE-Pim/Pi has a new Member! |
197 | It is called PWM/Pi (Passwordmanager/platform-independent) | 205 | It is called PWM/Pi (Passwordmanager/platform-independent) |
198 | and it is available for the Zaurus. | 206 | and it is available for the Zaurus. |
199 | It is planned, that it will be available later for Windows. | 207 | It is planned, that it will be available later for Windows. |
200 | (And for Linux, of course). | 208 | (And for Linux, of course). |
201 | It is a port of the Passwordmanager of KDE. | 209 | It is a port of the Passwordmanager of KDE. |
202 | It will need the MicroKDElibs to run. | 210 | It will need the MicroKDElibs to run. |
203 | 211 | ||
204 | Made loading of addressbooks in KA/Pi up to 7 times faster! | 212 | Made loading of addressbooks in KA/Pi up to 7 times faster! |
205 | The bigger your addressbook file, the more starting speed | 213 | The bigger your addressbook file, the more starting speed |
206 | will you gain. (relatively) | 214 | will you gain. (relatively) |
207 | 215 | ||
208 | The Qtopia addressbook connector is now platform independend | 216 | The Qtopia addressbook connector is now platform independend |
209 | as well and should work on any platform for importing/exporting | 217 | as well and should work on any platform for importing/exporting |
210 | Qtopia and Opie XML files. | 218 | Qtopia and Opie XML files. |
211 | 219 | ||
212 | Added a +30min feature to the timezone settings to make | 220 | Added a +30min feature to the timezone settings to make |
213 | KDE-Pim/Pi useable in Australia and other parts on the | 221 | KDE-Pim/Pi useable in Australia and other parts on the |
214 | world with strange timezones ;-) | 222 | world with strange timezones ;-) |
215 | 223 | ||
216 | German "Umlaute" should now be sorted correctly on the Z in KA/Pi. | 224 | German "Umlaute" should now be sorted correctly on the Z in KA/Pi. |
217 | 225 | ||
218 | It is now possible to disable the | 226 | It is now possible to disable the |
219 | "receive data via infrared" feature, such that syncing with | 227 | "receive data via infrared" feature, such that syncing with |
220 | Outlook is now possible again with Kx/Pi runing. | 228 | Outlook is now possible again with Kx/Pi runing. |
221 | Please disable it, before syncing Sharp DTM with Outlook. | 229 | Please disable it, before syncing Sharp DTM with Outlook. |
222 | For your convenience, the "receive data via infrared" feature | 230 | For your convenience, the "receive data via infrared" feature |
223 | is disabled automatically, if you sync Kx/Pi with DTM. | 231 | is disabled automatically, if you sync Kx/Pi with DTM. |
224 | You have to enable it again manually after syncing. | 232 | You have to enable it again manually after syncing. |
225 | Enabling this feature makes it impossible to start the | 233 | Enabling this feature makes it impossible to start the |
226 | Sharp DTM apps. If this feature is enabled, you will only get the | 234 | Sharp DTM apps. If this feature is enabled, you will only get the |
227 | alarm notification from KO/Pi and not from the Sharp calendar. | 235 | alarm notification from KO/Pi and not from the Sharp calendar. |
228 | This is very useful if you sync KO/Pi with Sharp DTM, | 236 | This is very useful if you sync KO/Pi with Sharp DTM, |
229 | because after syncing you usually would get notified about | 237 | because after syncing you usually would get notified about |
230 | an alarm by KO/Pi and the Sharp Calendar. | 238 | an alarm by KO/Pi and the Sharp Calendar. |
231 | 239 | ||
232 | Together with the Linux desktop version of KO/Pi | 240 | Together with the Linux desktop version of KO/Pi |
233 | it is now possible to sync KO/Pi on the Zaurus | 241 | it is now possible to sync KO/Pi on the Zaurus |
234 | with the complete KDE-desktop (3.3 or later) | 242 | with the complete KDE-desktop (3.3 or later) |
235 | calendar data easily. | 243 | calendar data easily. |
236 | That makes it possible to sync the Z with one | 244 | That makes it possible to sync the Z with one |
237 | click of a mouse with the KDE-Desktop. | 245 | click of a mouse with the KDE-Desktop. |
238 | This feature it available for all Zaurus platforms KO/Pi | 246 | This feature it available for all Zaurus platforms KO/Pi |
239 | is running on. | 247 | is running on. |
240 | The only thing needed is a running KO/Pi on Linux and | 248 | The only thing needed is a running KO/Pi on Linux and |
241 | a compiled version of the small | 249 | a compiled version of the small |
242 | KDE-Pim/Pi<->KDE-Desktop access command line program, | 250 | KDE-Pim/Pi<->KDE-Desktop access command line program, |
243 | which is in the KDE-Pim/Pi sources available. | 251 | which is in the KDE-Pim/Pi sources available. |
244 | 252 | ||
245 | The "KDE-desktop" syncing feature for KA/Pi will follow | 253 | The "KDE-desktop" syncing feature for KA/Pi will follow |
246 | in the next releases. | 254 | in the next releases. |
247 | 255 | ||
248 | Fixed the vcard export bug, which had the version 1.9.8. | 256 | Fixed the vcard export bug, which had the version 1.9.8. |
249 | 257 | ||
250 | Added missing GERMAN translation to KO/Pi. | 258 | Added missing GERMAN translation to KO/Pi. |
251 | Hi PsionX, could you add the missing french translation?Thx! | 259 | Hi PsionX, could you add the missing french translation?Thx! |
252 | 260 | ||
253 | Translation files for KA/Pi are available as well. | 261 | Translation files for KA/Pi are available as well. |
254 | GERMAN translation will be available in the next release. | 262 | GERMAN translation will be available in the next release. |
255 | PsionX ( yres, you again ;-) ), could you start translating | 263 | PsionX ( yres, you again ;-) ), could you start translating |
256 | KA/Pi? Thx! | 264 | KA/Pi? Thx! |
257 | 265 | ||
258 | You can download the version 1.9.9 at | 266 | You can download the version 1.9.9 at |
259 | 267 | ||
260 | http://sourceforge.net/project/showfiles.php?group_id=104103&package_id=112604 | 268 | http://sourceforge.net/project/showfiles.php?group_id=104103&package_id=112604 |
261 | 269 | ||
262 | Note: | 270 | Note: |
263 | To run the mail program OM/Pi you need libopenssl. | 271 | To run the mail program OM/Pi you need libopenssl. |
264 | A link to a download loaction is available at | 272 | A link to a download loaction is available at |
265 | ZSI at www.killefiz.de | 273 | ZSI at www.killefiz.de |
266 | 274 | ||
267 | 275 | ||
268 | ********** VERSION 1.9.8 ************ | 276 | ********** VERSION 1.9.8 ************ |
269 | 277 | ||
270 | Fixed character decoding in OM/Pi. | 278 | Fixed character decoding in OM/Pi. |
271 | (e.g. German "Umlaute" were not displayed properly.) | 279 | (e.g. German "Umlaute" were not displayed properly.) |
272 | 280 | ||
273 | Made is possible to reparent todos in KO/Pi. | 281 | Made is possible to reparent todos in KO/Pi. |
274 | Use contextmenu or keys (look at Help-Keys + Colors) for that. | 282 | Use contextmenu or keys (look at Help-Keys + Colors) for that. |
275 | 283 | ||
276 | Added the missing Sync-Howto and WhatsNew to the packages. | 284 | Added the missing Sync-Howto and WhatsNew to the packages. |
277 | 285 | ||
278 | KO/Pi on Linux desktop can now sync with KDE desktop. | 286 | KO/Pi on Linux desktop can now sync with KDE desktop. |
279 | That means: When using KO/Pi on Linux desktop for syncing with | 287 | That means: When using KO/Pi on Linux desktop for syncing with |
280 | KDE desktop and the Zaurus, the Zaurus can be synced now | 288 | KDE desktop and the Zaurus, the Zaurus can be synced now |
281 | with all KDE-Calendar resources, not only with one local file. | 289 | with all KDE-Calendar resources, not only with one local file. |
282 | (That makes it possible to sync the Zaurus with the | 290 | (That makes it possible to sync the Zaurus with the |
283 | calendar data on a Kolab server) | 291 | calendar data on a Kolab server) |
284 | 292 | ||
285 | KA/Pi syncing with KDE desktop will be available in the next version. | 293 | KA/Pi syncing with KDE desktop will be available in the next version. |
286 | 294 | ||