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