-rw-r--r-- | bin/kdepim/WhatsNew.txt | 3 |
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 | |||
@@ -1,87 +1,90 @@ | |||
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 2.1.13 ************ | 3 | ********** VERSION 2.1.13 ************ |
4 | 4 | ||
5 | Fixed a problem in KA/Pi search. | 5 | Fixed a problem in KA/Pi search. |
6 | Fixed some minor problems in KO/Pi. | 6 | Fixed some minor problems in KO/Pi. |
7 | Added calendar selection possibility to the todo view popup and to the event/todo/journal editor. | 7 | Added calendar selection possibility to the todo view popup and to the event/todo/journal editor. |
8 | 8 | ||
9 | Fixed memory usage problems in KA/Pi: | 9 | Fixed memory usage problems in KA/Pi: |
10 | When loading data KA/Pi did load the file data twice. | 10 | When loading data KA/Pi did load the file data twice. |
11 | Example: | 11 | Example: |
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. |
14 | When saving data KA/Pi did consume a lot of memory for the data parsing during the save process. | 14 | When saving data KA/Pi did consume a lot of memory for the data parsing during the save process. |
15 | This is fixed. | 15 | This is fixed. |
16 | Example: | 16 | Example: |
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. |
20 | Note: The memory usage of KA/Pi after the data is loaded/saved has not changed. | 20 | Note: The memory usage of KA/Pi after the data is loaded/saved has not changed. |
21 | The saving of data may be a bit slower now. | ||
21 | 22 | ||
22 | Fixed memory usage problems in KO/Pi: | 23 | Fixed memory usage problems in KO/Pi: |
23 | When KO/Pi did save the data to file, it did not release the used buffers after saving. | 24 | When KO/Pi did save the data to file, it did not release the used buffers after saving. |
24 | The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation. | 25 | The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation. |
25 | This is fixed. | 26 | This is fixed. |
26 | Example: | 27 | Example: |
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 | ||
29 | Optimized memory usage in KO/Pi Agenda view: | 30 | Optimized memory usage in KO/Pi Agenda view: |
30 | KO/Pi is storing some paint information in extra buffers for faster repainting of the agenda view. | 31 | KO/Pi is storing some paint information in extra buffers for faster repainting of the agenda view. |
31 | These buffers were not made smaller (i.e. downsized) because of performance reasons. | 32 | These buffers were not made smaller (i.e. downsized) because of performance reasons. |
32 | The handling of these buffers are now much smarter: | 33 | The handling of these buffers are now much smarter: |
33 | Two (of six) buffers are removed completely. | 34 | Two (of six) buffers are removed completely. |
34 | The remaing four buffers are now downsized after not using the agenda view for 45 seconds. | 35 | The remaing four buffers are now downsized after not using the agenda view for 45 seconds. |
35 | Such 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 | Such 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 | ||
37 | Worst case example ( for a maximum size agenda content): | 38 | Worst 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 | ||
41 | When 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 | |||
40 | Summary: | 43 | Summary: |
41 | Many memory wasting problems of KA/Pi and KO/Pi fixed such that it is better to use on the Zaurus. | 44 | Many 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 | ||
45 | KO/Pi: | 48 | KO/Pi: |
46 | Many small usability fixes, e.g. rearranged the popup menus such that they are better to use on the Zaurus. | 49 | Many small usability fixes, e.g. rearranged the popup menus such that they are better to use on the Zaurus. |
47 | Fixed a problem with the month view when file was saved but KO/Pi was not the active window. | 50 | Fixed a problem with the month view when file was saved but KO/Pi was not the active window. |
48 | Fixed some problems in the resource config dialog (e.g. added a warning if you set all calendars to read-only). | 51 | Fixed some problems in the resource config dialog (e.g. added a warning if you set all calendars to read-only). |
49 | Fixed some other small problems. | 52 | Fixed some other small problems. |
50 | 53 | ||
51 | ********** VERSION 2.1.11 ************ | 54 | ********** VERSION 2.1.11 ************ |
52 | 55 | ||
53 | KO/Pi: | 56 | KO/Pi: |
54 | Because we can have many calendars now in KO/Pi we can have more than one journal entry per day. | 57 | Because we can have many calendars now in KO/Pi we can have more than one journal entry per day. |
55 | Added features to handle (and add ) more than one journal entry per day. | 58 | Added features to handle (and add ) more than one journal entry per day. |
56 | Added option for a journal title. | 59 | Added option for a journal title. |
57 | 60 | ||
58 | Added info about the calendar, the item belongs to, to the event/todo/journal viewer. | 61 | Added info about the calendar, the item belongs to, to the event/todo/journal viewer. |
59 | Fixed a problem of the alarm of completed recurring todos. | 62 | Fixed a problem of the alarm of completed recurring todos. |
60 | Added to the event/todo editor to set quickly the category of an item. | 63 | Added to the event/todo editor to set quickly the category of an item. |
61 | 64 | ||
62 | 65 | ||
63 | Fixed some problems when calling KO/Pi or KA/Pi from the alarm applet. | 66 | Fixed some problems when calling KO/Pi or KA/Pi from the alarm applet. |
64 | 67 | ||
65 | Added KA/Pi multi sync to the multi sync called from the alarm applet. | 68 | Added KA/Pi multi sync to the multi sync called from the alarm applet. |
66 | 69 | ||
67 | ********** VERSION 2.1.10 ************ | 70 | ********** VERSION 2.1.10 ************ |
68 | 71 | ||
69 | KO/Pi: | 72 | KO/Pi: |
70 | Importing Birthdays will now create another file resource "Birthdays" and import the birthday data from KA/Pi into that file. | 73 | Importing Birthdays will now create another file resource "Birthdays" and import the birthday data from KA/Pi into that file. |
71 | When a multidayevent is selected in monthview all occurences of this event in the monthview are now hightlighted. | 74 | When a multidayevent is selected in monthview all occurences of this event in the monthview are now hightlighted. |
72 | Fixed a bug in searching for a small timerange, i.e. one day. | 75 | Fixed a bug in searching for a small timerange, i.e. one day. |
73 | 76 | ||
74 | KA/Pi: | 77 | KA/Pi: |
75 | Fixed two problems in csv export. | 78 | Fixed two problems in csv export. |
76 | Fixed problems when calling the contact selection dialog from KO/Pi or OM/Pi. | 79 | Fixed problems when calling the contact selection dialog from KO/Pi or OM/Pi. |
77 | 80 | ||
78 | ********** VERSION 2.1.9 ************ | 81 | ********** VERSION 2.1.9 ************ |
79 | 82 | ||
80 | KO/Pi: | 83 | KO/Pi: |
81 | Fixed some problems of the new search options in the search dialog. | 84 | Fixed some problems of the new search options in the search dialog. |
82 | Fixed some problems in the new resource config options. | 85 | Fixed some problems in the new resource config options. |
83 | Changed the recurrence edit of events and todos such that the recurrence edit page now is notified about a change of the start date on the first page. | 86 | Changed the recurrence edit of events and todos such that the recurrence edit page now is notified about a change of the start date on the first page. |
84 | Fixed a problem creating new events in the agenda view if at the day/time is already an agenda item shown: | 87 | Fixed a problem creating new events in the agenda view if at the day/time is already an agenda item shown: |
85 | Now you can click on the bottom/top of an allday agenda item or on the left/right side of an agenda item to get the "new todo/new event" popup. | 88 | Now you can click on the bottom/top of an allday agenda item or on the left/right side of an agenda item to get the "new todo/new event" popup. |
86 | 89 | ||
87 | Fixed a problem in recurrence range in syncing with DTM. | 90 | Fixed a problem in recurrence range in syncing with DTM. |