-rw-r--r-- | bin/kdepim/WhatsNew.txt | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/bin/kdepim/WhatsNew.txt b/bin/kdepim/WhatsNew.txt index 2ce78c7..2fd89f1 100644 --- a/bin/kdepim/WhatsNew.txt +++ b/bin/kdepim/WhatsNew.txt | |||
@@ -1,98 +1,105 @@ | |||
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.15 ************ | ||
4 | |||
5 | Fixed two layout problems on the Z: | ||
6 | Made the with of the newly added buttons on the Quick-Todo smaller. | ||
7 | Made listweek layout in 2 columns on the Z760 in portait screen and full menubar visible. | ||
8 | |||
9 | |||
3 | ********** VERSION 2.1.14 ************ | 10 | ********** VERSION 2.1.14 ************ |
4 | 11 | ||
5 | Added 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. | 12 | Added 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. |
6 | Added a button to add a subtodo quickly. | 13 | Added a button to add a subtodo quickly. |
7 | 14 | ||
8 | Added a possibility to search for conflicting events. (In the Action menu. Keyboard shortcut "q", shift+q or ctrl +q ). | 15 | Added a possibility to search for conflicting events. (In the Action menu. Keyboard shortcut "q", shift+q or ctrl +q ). |
9 | Added an option to change the layout of the list week to column mode. | 16 | Added an option to change the layout of the list week to column mode. |
10 | 17 | ||
11 | Fixed some usability problems in pi-sync mode by adding some progress information about file transfer. | 18 | Fixed some usability problems in pi-sync mode by adding some progress information about file transfer. |
12 | 19 | ||
13 | Fixed pi-sync problems with the new multi calendar feature. | 20 | Fixed pi-sync problems with the new multi calendar feature. |
14 | Now pi-sync behaviour should be: | 21 | Now pi-sync behaviour should be: |
15 | 1) Local sends file request ( as usual ) | 22 | 1) Local sends file request ( as usual ) |
16 | 2) Remote sends file which contains data of all enabled ( the calendar where the "eye" column is checked ) calendars. | 23 | 2) Remote sends file which contains data of all enabled ( the calendar where the "eye" column is checked ) calendars. |
17 | 3) Local syncs with data, adds new entries to default calendar and sends file back ( as usual ). | 24 | 3) Local syncs with data, adds new entries to default calendar and sends file back ( as usual ). |
18 | 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. | 25 | 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. |
19 | 4) Remote updates the data and adds new entries to default calendar. Readonly entries are not changed on remote. | 26 | 4) Remote updates the data and adds new entries to default calendar. Readonly entries are not changed on remote. |
20 | 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. | 27 | 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. |
21 | 28 | ||
22 | Summary: | 29 | Summary: |
23 | No 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. | 30 | No 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. |
24 | If you have different calendars on remote and local and some of them disabled you may get some "strange" bahaviour. | 31 | If you have different calendars on remote and local and some of them disabled you may get some "strange" bahaviour. |
25 | Well, the syncing has become quite complicated ... you should have no problems if you enable all calendars. | 32 | Well, the syncing has become quite complicated ... you should have no problems if you enable all calendars. |
26 | 33 | ||
27 | ********** VERSION 2.1.13 ************ | 34 | ********** VERSION 2.1.13 ************ |
28 | 35 | ||
29 | Fixed a problem in KA/Pi search. | 36 | Fixed a problem in KA/Pi search. |
30 | Fixed some minor problems in KO/Pi. | 37 | Fixed some minor problems in KO/Pi. |
31 | Added calendar selection possibility to the todo view popup and to the event/todo/journal editor. | 38 | Added calendar selection possibility to the todo view popup and to the event/todo/journal editor. |
32 | 39 | ||
33 | Fixed memory usage problems in KA/Pi: | 40 | Fixed memory usage problems in KA/Pi: |
34 | When loading data KA/Pi did load the file data twice. | 41 | When loading data KA/Pi did load the file data twice. |
35 | Example: | 42 | Example: |
36 | A 600k file did consume 1200k memory during loading process. | 43 | A 600k file did consume 1200k memory during loading process. |
37 | This is fixed, it does now consume only 600k during loading process. | 44 | This is fixed, it does now consume only 600k during loading process. |
38 | When saving data KA/Pi did consume a lot of memory for the data parsing during the save process. | 45 | When saving data KA/Pi did consume a lot of memory for the data parsing during the save process. |
39 | This is fixed. | 46 | This is fixed. |
40 | Example: | 47 | Example: |
41 | Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram. | 48 | Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram. |
42 | 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. | 49 | 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. |
43 | Now KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process. | 50 | Now KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process. |
44 | Note: The memory usage of KA/Pi after the data is loaded/saved has not changed. | 51 | Note: The memory usage of KA/Pi after the data is loaded/saved has not changed. |
45 | The saving of data may be a bit slower now. | 52 | The saving of data may be a bit slower now. |
46 | 53 | ||
47 | Fixed memory usage problems in KO/Pi: | 54 | Fixed memory usage problems in KO/Pi: |
48 | When KO/Pi did save the data to file, it did not release the used buffers after saving. | 55 | When KO/Pi did save the data to file, it did not release the used buffers after saving. |
49 | The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation. | 56 | The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation. |
50 | This is fixed. | 57 | This is fixed. |
51 | Example: | 58 | Example: |
52 | When saving a 400k file KO/Pi do now use 400k less memory now. | 59 | When saving a 400k file KO/Pi do now use 400k less memory now. |
53 | 60 | ||
54 | Optimized memory usage in KO/Pi Agenda view: | 61 | Optimized memory usage in KO/Pi Agenda view: |
55 | KO/Pi is storing some paint information in extra buffers for faster repainting of the agenda view. | 62 | KO/Pi is storing some paint information in extra buffers for faster repainting of the agenda view. |
56 | These buffers were not made smaller (i.e. downsized) because of performance reasons. | 63 | These buffers were not made smaller (i.e. downsized) because of performance reasons. |
57 | The handling of these buffers are now much smarter: | 64 | The handling of these buffers are now much smarter: |
58 | Two (of six) buffers are removed completely. | 65 | Two (of six) buffers are removed completely. |
59 | The remaing four buffers are now downsized after not using the agenda view for 45 seconds. | 66 | The remaing four buffers are now downsized after not using the agenda view for 45 seconds. |
60 | 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. | 67 | 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. |
61 | 68 | ||
62 | Worst case example ( for a maximum size agenda content): | 69 | Worst case example ( for a maximum size agenda content): |
63 | 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. | 70 | 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. |
64 | 71 | ||
65 | 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. | 72 | 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. |
66 | 73 | ||
67 | Summary: | 74 | Summary: |
68 | Many memory wasting problems of KA/Pi and KO/Pi fixed such that it is better to use on the Zaurus. | 75 | Many memory wasting problems of KA/Pi and KO/Pi fixed such that it is better to use on the Zaurus. |
69 | 76 | ||
70 | ********** VERSION 2.1.12 ************ | 77 | ********** VERSION 2.1.12 ************ |
71 | 78 | ||
72 | KO/Pi: | 79 | KO/Pi: |
73 | Many small usability fixes, e.g. rearranged the popup menus such that they are better to use on the Zaurus. | 80 | Many small usability fixes, e.g. rearranged the popup menus such that they are better to use on the Zaurus. |
74 | Fixed a problem with the month view when file was saved but KO/Pi was not the active window. | 81 | Fixed a problem with the month view when file was saved but KO/Pi was not the active window. |
75 | Fixed some problems in the resource config dialog (e.g. added a warning if you set all calendars to read-only). | 82 | Fixed some problems in the resource config dialog (e.g. added a warning if you set all calendars to read-only). |
76 | Fixed some other small problems. | 83 | Fixed some other small problems. |
77 | 84 | ||
78 | ********** VERSION 2.1.11 ************ | 85 | ********** VERSION 2.1.11 ************ |
79 | 86 | ||
80 | KO/Pi: | 87 | KO/Pi: |
81 | Because we can have many calendars now in KO/Pi we can have more than one journal entry per day. | 88 | Because we can have many calendars now in KO/Pi we can have more than one journal entry per day. |
82 | Added features to handle (and add ) more than one journal entry per day. | 89 | Added features to handle (and add ) more than one journal entry per day. |
83 | Added option for a journal title. | 90 | Added option for a journal title. |
84 | 91 | ||
85 | Added info about the calendar, the item belongs to, to the event/todo/journal viewer. | 92 | Added info about the calendar, the item belongs to, to the event/todo/journal viewer. |
86 | Fixed a problem of the alarm of completed recurring todos. | 93 | Fixed a problem of the alarm of completed recurring todos. |
87 | Added to the event/todo editor to set quickly the category of an item. | 94 | Added to the event/todo editor to set quickly the category of an item. |
88 | 95 | ||
89 | 96 | ||
90 | Fixed some problems when calling KO/Pi or KA/Pi from the alarm applet. | 97 | Fixed some problems when calling KO/Pi or KA/Pi from the alarm applet. |
91 | 98 | ||
92 | Added KA/Pi multi sync to the multi sync called from the alarm applet. | 99 | Added KA/Pi multi sync to the multi sync called from the alarm applet. |
93 | 100 | ||
94 | ********** VERSION 2.1.10 ************ | 101 | ********** VERSION 2.1.10 ************ |
95 | 102 | ||
96 | KO/Pi: | 103 | KO/Pi: |
97 | Importing Birthdays will now create another file resource "Birthdays" and import the birthday data from KA/Pi into that file. | 104 | Importing Birthdays will now create another file resource "Birthdays" and import the birthday data from KA/Pi into that file. |
98 | When a multidayevent is selected in monthview all occurences of this event in the monthview are now hightlighted. | 105 | When a multidayevent is selected in monthview all occurences of this event in the monthview are now hightlighted. |