summaryrefslogtreecommitdiffabout
Unidiff
Diffstat (more/less context) (ignore whitespace changes)
-rw-r--r--bin/kdepim/WhatsNew.txt3
1 files changed, 3 insertions, 0 deletions
diff --git a/bin/kdepim/WhatsNew.txt b/bin/kdepim/WhatsNew.txt
index ea49c2c..d6b2dc7 100644
--- a/bin/kdepim/WhatsNew.txt
+++ b/bin/kdepim/WhatsNew.txt
@@ -9,43 +9,46 @@ Added calendar selection possibility to the todo view popup and to the event/tod
9Fixed memory usage problems in KA/Pi: 9Fixed memory usage problems in KA/Pi:
10When loading data KA/Pi did load the file data twice. 10When loading data KA/Pi did load the file data twice.
11Example: 11Example:
12 A 600k file did consume 1200k memory during loading process. 12 A 600k file did consume 1200k memory during loading process.
13 This is fixed, it does now consume only 600k during loading process. 13 This is fixed, it does now consume only 600k during loading process.
14When saving data KA/Pi did consume a lot of memory for the data parsing during the save process. 14When saving data KA/Pi did consume a lot of memory for the data parsing during the save process.
15This is fixed. 15This is fixed.
16Example: 16Example:
17 Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram. 17 Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram.
18 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. 18 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.
19 Now KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process. 19 Now KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process.
20Note: The memory usage of KA/Pi after the data is loaded/saved has not changed. 20Note: The memory usage of KA/Pi after the data is loaded/saved has not changed.
21The saving of data may be a bit slower now.
21 22
22Fixed memory usage problems in KO/Pi: 23Fixed memory usage problems in KO/Pi:
23When KO/Pi did save the data to file, it did not release the used buffers after saving. 24When KO/Pi did save the data to file, it did not release the used buffers after saving.
24The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation. 25The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation.
25This is fixed. 26This is fixed.
26Example: 27Example:
27 When saving a 400k file KO/Pi do now use 400k less memory now. 28 When saving a 400k file KO/Pi do now use 400k less memory now.
28 29
29Optimized memory usage in KO/Pi Agenda view: 30Optimized memory usage in KO/Pi Agenda view:
30KO/Pi is storing some paint information in extra buffers for faster repainting of the agenda view. 31KO/Pi is storing some paint information in extra buffers for faster repainting of the agenda view.
31These buffers were not made smaller (i.e. downsized) because of performance reasons. 32These buffers were not made smaller (i.e. downsized) because of performance reasons.
32The handling of these buffers are now much smarter: 33The handling of these buffers are now much smarter:
33Two (of six) buffers are removed completely. 34Two (of six) buffers are removed completely.
34The remaing four buffers are now downsized after not using the agenda view for 45 seconds. 35The remaing four buffers are now downsized after not using the agenda view for 45 seconds.
35Such 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. 36Such 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.
36 37
37Worst case example ( for a maximum size agenda content): 38Worst case example ( for a maximum size agenda content):
38 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. 39 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.
39 40
41When 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.
42
40Summary: 43Summary:
41Many memory wasting problems of KA/Pi and KO/Pi fixed such that it is better to use on the Zaurus. 44Many memory wasting problems of KA/Pi and KO/Pi fixed such that it is better to use on the Zaurus.
42 45
43********** VERSION 2.1.12 ************ 46********** VERSION 2.1.12 ************
44 47
45KO/Pi: 48KO/Pi:
46Many small usability fixes, e.g. rearranged the popup menus such that they are better to use on the Zaurus. 49Many small usability fixes, e.g. rearranged the popup menus such that they are better to use on the Zaurus.
47Fixed a problem with the month view when file was saved but KO/Pi was not the active window. 50Fixed a problem with the month view when file was saved but KO/Pi was not the active window.
48Fixed some problems in the resource config dialog (e.g. added a warning if you set all calendars to read-only). 51Fixed some problems in the resource config dialog (e.g. added a warning if you set all calendars to read-only).
49Fixed some other small problems. 52Fixed some other small problems.
50 53
51********** VERSION 2.1.11 ************ 54********** VERSION 2.1.11 ************