summaryrefslogtreecommitdiffabout
path: root/bin/kdepim
Unidiff
Diffstat (limited to 'bin/kdepim') (more/less context) (ignore whitespace changes)
-rw-r--r--bin/kdepim/WhatsNew.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/bin/kdepim/WhatsNew.txt b/bin/kdepim/WhatsNew.txt
index 3da24c5..8127ef4 100644
--- a/bin/kdepim/WhatsNew.txt
+++ b/bin/kdepim/WhatsNew.txt
@@ -1,101 +1,101 @@
1Info about the changes in new versions of KDE-Pim/Pi 1Info about the changes in new versions of KDE-Pim/Pi
2 2
3********** VERSION 2.1.16 ************ 3********** VERSION 2.1.16 ************
4 4
5 5Fixed a problem with the menu bar in KO/Pi and using the "Menu" hardware key on the Zaurus.
6 6
7********** VERSION 2.1.15 ************ 7********** VERSION 2.1.15 ************
8 8
9Fixed two layout problems on the Z: 9Fixed two layout problems on the Z:
10Made the with of the newly added buttons on the Quick-Todo smaller. 10Made the with of the newly added buttons on the Quick-Todo smaller.
11Made listweek layout in 2 columns on the Z760 in portait screen and full menubar visible. 11Made listweek layout in 2 columns on the Z760 in portait screen and full menubar visible.
12 12
13 13
14********** VERSION 2.1.14 ************ 14********** VERSION 2.1.14 ************
15 15
16Added some buttons to the KO/Pi Quick-todo line to make it possible to quickly access some todo view layout settings like display all flat/open/close and hide/show running/done. 16Added some buttons to the KO/Pi Quick-todo line to make it possible to quickly access some todo view layout settings like display all flat/open/close and hide/show running/done.
17Added a button to add a subtodo quickly. 17Added a button to add a subtodo quickly.
18 18
19Added a possibility to search for conflicting events. (In the Action menu. Keyboard shortcut "q", shift+q or ctrl +q ). 19Added a possibility to search for conflicting events. (In the Action menu. Keyboard shortcut "q", shift+q or ctrl +q ).
20Added an option to change the layout of the list week to column mode. 20Added an option to change the layout of the list week to column mode.
21 21
22Fixed some usability problems in pi-sync mode by adding some progress information about file transfer. 22Fixed some usability problems in pi-sync mode by adding some progress information about file transfer.
23 23
24Fixed pi-sync problems with the new multi calendar feature. 24Fixed pi-sync problems with the new multi calendar feature.
25Now pi-sync behaviour should be: 25Now pi-sync behaviour should be:
261) Local sends file request ( as usual ) 261) Local sends file request ( as usual )
272) Remote sends file which contains data of all enabled ( the calendar where the "eye" column is checked ) calendars. 272) Remote sends file which contains data of all enabled ( the calendar where the "eye" column is checked ) calendars.
283) Local syncs with data, adds new entries to default calendar and sends file back ( as usual ). 283) Local syncs with data, adds new entries to default calendar and sends file back ( as usual ).
29 If the data which local receives contains entries which are on disabled calendars on local this entries are updated and not added as duplicates to the default calendar. 29 If the data which local receives contains entries which are on disabled calendars on local this entries are updated and not added as duplicates to the default calendar.
304) Remote updates the data and adds new entries to default calendar. Readonly entries are not changed on remote. 304) Remote updates the data and adds new entries to default calendar. Readonly entries are not changed on remote.
31 If the data which remote receives contains entries which are on disabled calendars on remote this entries are updated and not added as duplicates to the default calendar. 31 If the data which remote receives contains entries which are on disabled calendars on remote this entries are updated and not added as duplicates to the default calendar.
32 32
33Summary: 33Summary:
34No new item ( new created after the last sync ) in a disabled calendar is propagated to the sync partner. Readonly items are synced and added/changed on the sync partner if it is not readonly on the sync partner. 34No new item ( new created after the last sync ) in a disabled calendar is propagated to the sync partner. Readonly items are synced and added/changed on the sync partner if it is not readonly on the sync partner.
35If you have different calendars on remote and local and some of them disabled you may get some "strange" bahaviour. 35If you have different calendars on remote and local and some of them disabled you may get some "strange" bahaviour.
36Well, the syncing has become quite complicated ... you should have no problems if you enable all calendars. 36Well, the syncing has become quite complicated ... you should have no problems if you enable all calendars.
37 37
38********** VERSION 2.1.13 ************ 38********** VERSION 2.1.13 ************
39 39
40Fixed a problem in KA/Pi search. 40Fixed a problem in KA/Pi search.
41Fixed some minor problems in KO/Pi. 41Fixed some minor problems in KO/Pi.
42Added calendar selection possibility to the todo view popup and to the event/todo/journal editor. 42Added calendar selection possibility to the todo view popup and to the event/todo/journal editor.
43 43
44Fixed memory usage problems in KA/Pi: 44Fixed memory usage problems in KA/Pi:
45When loading data KA/Pi did load the file data twice. 45When loading data KA/Pi did load the file data twice.
46Example: 46Example:
47 A 600k file did consume 1200k memory during loading process. 47 A 600k file did consume 1200k memory during loading process.
48 This is fixed, it does now consume only 600k during loading process. 48 This is fixed, it does now consume only 600k during loading process.
49When saving data KA/Pi did consume a lot of memory for the data parsing during the save process. 49When saving data KA/Pi did consume a lot of memory for the data parsing during the save process.
50This is fixed. 50This is fixed.
51Example: 51Example:
52 Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram. 52 Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram.
53 When saving KA/Pi did consume 28.6 Meg of Ram. That causes a crash on the Zaurus because there was no memeory left in the system. 53 When saving KA/Pi did consume 28.6 Meg of Ram. That causes a crash on the Zaurus because there was no memeory left in the system.
54 Now KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process. 54 Now KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process.
55Note: The memory usage of KA/Pi after the data is loaded/saved has not changed. 55Note: The memory usage of KA/Pi after the data is loaded/saved has not changed.
56The saving of data may be a bit slower now. 56The saving of data may be a bit slower now.
57 57
58Fixed memory usage problems in KO/Pi: 58Fixed memory usage problems in KO/Pi:
59When KO/Pi did save the data to file, it did not release the used buffers after saving. 59When KO/Pi did save the data to file, it did not release the used buffers after saving.
60The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation. 60The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation.
61This is fixed. 61This is fixed.
62Example: 62Example:
63 When saving a 400k file KO/Pi do now use 400k less memory now. 63 When saving a 400k file KO/Pi do now use 400k less memory now.
64 64
65Optimized memory usage in KO/Pi Agenda view: 65Optimized memory usage in KO/Pi Agenda view:
66KO/Pi is storing some paint information in extra buffers for faster repainting of the agenda view. 66KO/Pi is storing some paint information in extra buffers for faster repainting of the agenda view.
67These buffers were not made smaller (i.e. downsized) because of performance reasons. 67These buffers were not made smaller (i.e. downsized) because of performance reasons.
68The handling of these buffers are now much smarter: 68The handling of these buffers are now much smarter:
69Two (of six) buffers are removed completely. 69Two (of six) buffers are removed completely.
70The remaing four buffers are now downsized after not using the agenda view for 45 seconds. 70The remaing four buffers are now downsized after not using the agenda view for 45 seconds.
71Such that the memory usage of KO/Pi is smaller now in general ( because 2 buffers are removed) and is much smaller when not using the agenda view. That is very important when using fastload for KO/Pi. 71Such that the memory usage of KO/Pi is smaller now in general ( because 2 buffers are removed) and is much smaller when not using the agenda view. That is very important when using fastload for KO/Pi.
72 72
73Worst case example ( for a maximum size agenda content): 73Worst case example ( for a maximum size agenda content):
74 When resizing the agenda content to a large scale, KO/Pi did use 17Meg of mem ( and did not use less memory until it was stopped). Now KO/Pi is using on the same operation only 14.3 Meg of mem and after 45 seconds not using the agenda view it uses only 9.4 Meg of mem. 74 When resizing the agenda content to a large scale, KO/Pi did use 17Meg of mem ( and did not use less memory until it was stopped). Now KO/Pi is using on the same operation only 14.3 Meg of mem and after 45 seconds not using the agenda view it uses only 9.4 Meg of mem.
75 75
76When switching to an unused Agenda view now KO/Pi is upizing the buffers again. This takes less than a second. Such that switching to Agenda view (after not using it for more than 45 seconds) is now a bit slower. 76When switching to an unused Agenda view now KO/Pi is upizing the buffers again. This takes less than a second. Such that switching to Agenda view (after not using it for more than 45 seconds) is now a bit slower.
77 77
78Summary: 78Summary:
79Many memory wasting problems of KA/Pi and KO/Pi fixed such that it is better to use on the Zaurus. 79Many memory wasting problems of KA/Pi and KO/Pi fixed such that it is better to use on the Zaurus.
80 80
81********** VERSION 2.1.12 ************ 81********** VERSION 2.1.12 ************
82 82
83KO/Pi: 83KO/Pi:
84Many small usability fixes, e.g. rearranged the popup menus such that they are better to use on the Zaurus. 84Many small usability fixes, e.g. rearranged the popup menus such that they are better to use on the Zaurus.
85Fixed a problem with the month view when file was saved but KO/Pi was not the active window. 85Fixed a problem with the month view when file was saved but KO/Pi was not the active window.
86Fixed some problems in the resource config dialog (e.g. added a warning if you set all calendars to read-only). 86Fixed some problems in the resource config dialog (e.g. added a warning if you set all calendars to read-only).
87Fixed some other small problems. 87Fixed some other small problems.
88 88
89********** VERSION 2.1.11 ************ 89********** VERSION 2.1.11 ************
90 90
91KO/Pi: 91KO/Pi:
92Because we can have many calendars now in KO/Pi we can have more than one journal entry per day. 92Because we can have many calendars now in KO/Pi we can have more than one journal entry per day.
93Added features to handle (and add ) more than one journal entry per day. 93Added features to handle (and add ) more than one journal entry per day.
94Added option for a journal title. 94Added option for a journal title.
95 95
96Added info about the calendar, the item belongs to, to the event/todo/journal viewer. 96Added info about the calendar, the item belongs to, to the event/todo/journal viewer.
97Fixed a problem of the alarm of completed recurring todos. 97Fixed a problem of the alarm of completed recurring todos.
98Added to the event/todo editor to set quickly the category of an item. 98Added to the event/todo editor to set quickly the category of an item.
99 99
100 100
101Fixed some problems when calling KO/Pi or KA/Pi from the alarm applet. 101Fixed some problems when calling KO/Pi or KA/Pi from the alarm applet.