author | zautrix <zautrix> | 2005-07-10 09:20:29 (UTC) |
---|---|---|
committer | zautrix <zautrix> | 2005-07-10 09:20:29 (UTC) |
commit | e8b6635ef7c98996f0415e6a77394569493ab151 (patch) (unidiff) | |
tree | 70fbf03e2ce62730fb8dddc288264c916e18d14e | |
parent | 2a3542ecc4eee8bb4b3d81fcf69e0cf97f07ff4a (diff) | |
download | kdepimpi-e8b6635ef7c98996f0415e6a77394569493ab151.zip kdepimpi-e8b6635ef7c98996f0415e6a77394569493ab151.tar.gz kdepimpi-e8b6635ef7c98996f0415e6a77394569493ab151.tar.bz2 |
version
-rw-r--r-- | bin/kdepim/WhatsNew.txt | 4 | ||||
-rw-r--r-- | desktop/rpm/kdepim_rpm | 2 | ||||
-rw-r--r-- | version | 2 |
3 files changed, 6 insertions, 2 deletions
diff --git a/bin/kdepim/WhatsNew.txt b/bin/kdepim/WhatsNew.txt index 2fd89f1..3da24c5 100644 --- a/bin/kdepim/WhatsNew.txt +++ b/bin/kdepim/WhatsNew.txt | |||
@@ -1,98 +1,102 @@ | |||
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 ************ | ||
4 | |||
5 | |||
6 | |||
3 | ********** VERSION 2.1.15 ************ | 7 | ********** VERSION 2.1.15 ************ |
4 | 8 | ||
5 | Fixed two layout problems on the Z: | 9 | Fixed two layout problems on the Z: |
6 | Made the with of the newly added buttons on the Quick-Todo smaller. | 10 | 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. | 11 | Made listweek layout in 2 columns on the Z760 in portait screen and full menubar visible. |
8 | 12 | ||
9 | 13 | ||
10 | ********** VERSION 2.1.14 ************ | 14 | ********** VERSION 2.1.14 ************ |
11 | 15 | ||
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. | 16 | 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. |
13 | Added a button to add a subtodo quickly. | 17 | Added a button to add a subtodo quickly. |
14 | 18 | ||
15 | Added a possibility to search for conflicting events. (In the Action menu. Keyboard shortcut "q", shift+q or ctrl +q ). | 19 | Added a possibility to search for conflicting events. (In the Action menu. Keyboard shortcut "q", shift+q or ctrl +q ). |
16 | Added an option to change the layout of the list week to column mode. | 20 | Added an option to change the layout of the list week to column mode. |
17 | 21 | ||
18 | Fixed some usability problems in pi-sync mode by adding some progress information about file transfer. | 22 | Fixed some usability problems in pi-sync mode by adding some progress information about file transfer. |
19 | 23 | ||
20 | Fixed pi-sync problems with the new multi calendar feature. | 24 | Fixed pi-sync problems with the new multi calendar feature. |
21 | Now pi-sync behaviour should be: | 25 | Now pi-sync behaviour should be: |
22 | 1) Local sends file request ( as usual ) | 26 | 1) Local sends file request ( as usual ) |
23 | 2) Remote sends file which contains data of all enabled ( the calendar where the "eye" column is checked ) calendars. | 27 | 2) Remote sends file which contains data of all enabled ( the calendar where the "eye" column is checked ) calendars. |
24 | 3) Local syncs with data, adds new entries to default calendar and sends file back ( as usual ). | 28 | 3) Local syncs with data, adds new entries to default calendar and sends file back ( as usual ). |
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. | 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. |
26 | 4) Remote updates the data and adds new entries to default calendar. Readonly entries are not changed on remote. | 30 | 4) Remote updates the data and adds new entries to default calendar. Readonly entries are not changed on remote. |
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. | 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. |
28 | 32 | ||
29 | Summary: | 33 | Summary: |
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. | 34 | 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. |
31 | If you have different calendars on remote and local and some of them disabled you may get some "strange" bahaviour. | 35 | If you have different calendars on remote and local and some of them disabled you may get some "strange" bahaviour. |
32 | Well, the syncing has become quite complicated ... you should have no problems if you enable all calendars. | 36 | Well, the syncing has become quite complicated ... you should have no problems if you enable all calendars. |
33 | 37 | ||
34 | ********** VERSION 2.1.13 ************ | 38 | ********** VERSION 2.1.13 ************ |
35 | 39 | ||
36 | Fixed a problem in KA/Pi search. | 40 | Fixed a problem in KA/Pi search. |
37 | Fixed some minor problems in KO/Pi. | 41 | Fixed some minor problems in KO/Pi. |
38 | Added calendar selection possibility to the todo view popup and to the event/todo/journal editor. | 42 | Added calendar selection possibility to the todo view popup and to the event/todo/journal editor. |
39 | 43 | ||
40 | Fixed memory usage problems in KA/Pi: | 44 | Fixed memory usage problems in KA/Pi: |
41 | When loading data KA/Pi did load the file data twice. | 45 | When loading data KA/Pi did load the file data twice. |
42 | Example: | 46 | Example: |
43 | A 600k file did consume 1200k memory during loading process. | 47 | A 600k file did consume 1200k memory during loading process. |
44 | 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. |
45 | When saving data KA/Pi did consume a lot of memory for the data parsing during the save process. | 49 | When saving data KA/Pi did consume a lot of memory for the data parsing during the save process. |
46 | This is fixed. | 50 | This is fixed. |
47 | Example: | 51 | Example: |
48 | 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. |
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. | 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. |
50 | 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. |
51 | Note: The memory usage of KA/Pi after the data is loaded/saved has not changed. | 55 | Note: The memory usage of KA/Pi after the data is loaded/saved has not changed. |
52 | The saving of data may be a bit slower now. | 56 | The saving of data may be a bit slower now. |
53 | 57 | ||
54 | Fixed memory usage problems in KO/Pi: | 58 | Fixed memory usage problems in KO/Pi: |
55 | When KO/Pi did save the data to file, it did not release the used buffers after saving. | 59 | When KO/Pi did save the data to file, it did not release the used buffers after saving. |
56 | The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation. | 60 | The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation. |
57 | This is fixed. | 61 | This is fixed. |
58 | Example: | 62 | Example: |
59 | 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. |
60 | 64 | ||
61 | Optimized memory usage in KO/Pi Agenda view: | 65 | Optimized memory usage in KO/Pi Agenda view: |
62 | KO/Pi is storing some paint information in extra buffers for faster repainting of the agenda view. | 66 | KO/Pi is storing some paint information in extra buffers for faster repainting of the agenda view. |
63 | These buffers were not made smaller (i.e. downsized) because of performance reasons. | 67 | These buffers were not made smaller (i.e. downsized) because of performance reasons. |
64 | The handling of these buffers are now much smarter: | 68 | The handling of these buffers are now much smarter: |
65 | Two (of six) buffers are removed completely. | 69 | Two (of six) buffers are removed completely. |
66 | The remaing four buffers are now downsized after not using the agenda view for 45 seconds. | 70 | The remaing four buffers are now downsized after not using the agenda view for 45 seconds. |
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. | 71 | 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. |
68 | 72 | ||
69 | Worst case example ( for a maximum size agenda content): | 73 | Worst case example ( for a maximum size agenda content): |
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. | 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. |
71 | 75 | ||
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. | 76 | 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. |
73 | 77 | ||
74 | Summary: | 78 | Summary: |
75 | Many memory wasting problems of KA/Pi and KO/Pi fixed such that it is better to use on the Zaurus. | 79 | Many memory wasting problems of KA/Pi and KO/Pi fixed such that it is better to use on the Zaurus. |
76 | 80 | ||
77 | ********** VERSION 2.1.12 ************ | 81 | ********** VERSION 2.1.12 ************ |
78 | 82 | ||
79 | KO/Pi: | 83 | KO/Pi: |
80 | Many small usability fixes, e.g. rearranged the popup menus such that they are better to use on the Zaurus. | 84 | Many small usability fixes, e.g. rearranged the popup menus such that they are better to use on the Zaurus. |
81 | Fixed a problem with the month view when file was saved but KO/Pi was not the active window. | 85 | Fixed a problem with the month view when file was saved but KO/Pi was not the active window. |
82 | Fixed some problems in the resource config dialog (e.g. added a warning if you set all calendars to read-only). | 86 | Fixed some problems in the resource config dialog (e.g. added a warning if you set all calendars to read-only). |
83 | Fixed some other small problems. | 87 | Fixed some other small problems. |
84 | 88 | ||
85 | ********** VERSION 2.1.11 ************ | 89 | ********** VERSION 2.1.11 ************ |
86 | 90 | ||
87 | KO/Pi: | 91 | KO/Pi: |
88 | Because we can have many calendars now in KO/Pi we can have more than one journal entry per day. | 92 | Because we can have many calendars now in KO/Pi we can have more than one journal entry per day. |
89 | Added features to handle (and add ) more than one journal entry per day. | 93 | Added features to handle (and add ) more than one journal entry per day. |
90 | Added option for a journal title. | 94 | Added option for a journal title. |
91 | 95 | ||
92 | Added info about the calendar, the item belongs to, to the event/todo/journal viewer. | 96 | Added info about the calendar, the item belongs to, to the event/todo/journal viewer. |
93 | Fixed a problem of the alarm of completed recurring todos. | 97 | Fixed a problem of the alarm of completed recurring todos. |
94 | Added to the event/todo editor to set quickly the category of an item. | 98 | Added to the event/todo editor to set quickly the category of an item. |
95 | 99 | ||
96 | 100 | ||
97 | Fixed some problems when calling KO/Pi or KA/Pi from the alarm applet. | 101 | Fixed some problems when calling KO/Pi or KA/Pi from the alarm applet. |
98 | 102 | ||
diff --git a/desktop/rpm/kdepim_rpm b/desktop/rpm/kdepim_rpm index 50acdba..dc9c196 100644 --- a/desktop/rpm/kdepim_rpm +++ b/desktop/rpm/kdepim_rpm | |||
@@ -1,84 +1,84 @@ | |||
1 | Summary: A collection of PIM programs | 1 | Summary: A collection of PIM programs |
2 | Name: KDE-Pim-Pi | 2 | Name: KDE-Pim-Pi |
3 | Version: 2.1.15 | 3 | Version: 2.1.16 |
4 | Release: SuSE_9.2 | 4 | Release: SuSE_9.2 |
5 | Copyright:GPL | 5 | Copyright:GPL |
6 | Group: Productivity/Pim | 6 | Group: Productivity/Pim |
7 | Source:http://sourceforge.net/projects/kdepimpi/ | 7 | Source:http://sourceforge.net/projects/kdepimpi/ |
8 | URL:http://sourceforge.net/projects/kdepimpi/ | 8 | URL:http://sourceforge.net/projects/kdepimpi/ |
9 | Packager: zautrix | 9 | Packager: zautrix |
10 | 10 | ||
11 | %description | 11 | %description |
12 | This package contains the platform-independent PIM programs from | 12 | This package contains the platform-independent PIM programs from |
13 | www.pi-sync.info, compiled for SuSE 9.2: | 13 | www.pi-sync.info, compiled for SuSE 9.2: |
14 | KTimeTacker/Pi | 14 | KTimeTacker/Pi |
15 | KPhone/Pi | 15 | KPhone/Pi |
16 | KAddressbook/Pi | 16 | KAddressbook/Pi |
17 | KOrganizer/Pi | 17 | KOrganizer/Pi |
18 | PasswordManager/Pi | 18 | PasswordManager/Pi |
19 | KOPieMail/Pi | 19 | KOPieMail/Pi |
20 | 20 | ||
21 | These applications do not need anything from the KDE-desktop | 21 | These applications do not need anything from the KDE-desktop |
22 | at all to run on Linux. However, there is a dependency from | 22 | at all to run on Linux. However, there is a dependency from |
23 | two KDE libs, because a small command line program is included | 23 | two KDE libs, because a small command line program is included |
24 | to make it possible to sync with the KDE-desktop applications. | 24 | to make it possible to sync with the KDE-desktop applications. |
25 | 25 | ||
26 | These applications are independent from the KDE-desktop | 26 | These applications are independent from the KDE-desktop |
27 | environment. That means, nothing of your existing | 27 | environment. That means, nothing of your existing |
28 | KDE-desktop setup will be changed, or any data | 28 | KDE-desktop setup will be changed, or any data |
29 | (calendar-addressbook) used by the KDE-desktop | 29 | (calendar-addressbook) used by the KDE-desktop |
30 | applications will be changed or accessed. | 30 | applications will be changed or accessed. |
31 | These applications stores their data and config in | 31 | These applications stores their data and config in |
32 | $HOME/kdepim/ | 32 | $HOME/kdepim/ |
33 | However, because the same file format is used, | 33 | However, because the same file format is used, |
34 | an easy exchange of data with the KDE-desktop | 34 | an easy exchange of data with the KDE-desktop |
35 | is possible. | 35 | is possible. |
36 | A small command line program is included | 36 | A small command line program is included |
37 | to make it possible to sync with the KDE-desktop applications. | 37 | to make it possible to sync with the KDE-desktop applications. |
38 | You do not need to call this program from the commandline, | 38 | You do not need to call this program from the commandline, |
39 | it is called from the KDE-Pim/Pi apps when you choose there: | 39 | it is called from the KDE-Pim/Pi apps when you choose there: |
40 | Sync with KDE_Desktop. | 40 | Sync with KDE_Desktop. |
41 | If something is going wrong, please start the | 41 | If something is going wrong, please start the |
42 | KDE-Pim/Pi program itself from the console to get detailed output. | 42 | KDE-Pim/Pi program itself from the console to get detailed output. |
43 | 43 | ||
44 | After installation, you should have a | 44 | After installation, you should have a |
45 | PIM-pi | 45 | PIM-pi |
46 | folder in your KDE start menu, where you can | 46 | folder in your KDE start menu, where you can |
47 | start the applications from. | 47 | start the applications from. |
48 | 48 | ||
49 | These programs makes it possible to sync your Zaurus easily | 49 | These programs makes it possible to sync your Zaurus easily |
50 | (with the KDE-Pim/Pi programs running on the Zaurus) | 50 | (with the KDE-Pim/Pi programs running on the Zaurus) |
51 | with the KDE-desktop calendar/addressbook data. | 51 | with the KDE-desktop calendar/addressbook data. |
52 | If you want to use that, you have to update your | 52 | If you want to use that, you have to update your |
53 | KDE-desktop to version 3.3.0 or higher. | 53 | KDE-desktop to version 3.3.0 or higher. |
54 | SuSE 9.2 contains KDE 3.3.0 such that no update is needed. | 54 | SuSE 9.2 contains KDE 3.3.0 such that no update is needed. |
55 | Actually - after the (non difficult) configuration is set up - | 55 | Actually - after the (non difficult) configuration is set up - |
56 | with two mouseklicks on the Zaurus, | 56 | with two mouseklicks on the Zaurus, |
57 | the Zaurus syncs with the corresponding KDE-Pim/Pi | 57 | the Zaurus syncs with the corresponding KDE-Pim/Pi |
58 | program on the Linux Desktop which syncs automatically | 58 | program on the Linux Desktop which syncs automatically |
59 | with the KDE-desktop data. | 59 | with the KDE-desktop data. |
60 | 60 | ||
61 | If you want to use the KDE-desktop calendar/addressbook applications, | 61 | If you want to use the KDE-desktop calendar/addressbook applications, |
62 | just install these apps in this package and use them as a syncing tool for the | 62 | just install these apps in this package and use them as a syncing tool for the |
63 | Zaurus <-> KDE-desktop sync. | 63 | Zaurus <-> KDE-desktop sync. |
64 | The sync requires a network connection from your Zaurus to | 64 | The sync requires a network connection from your Zaurus to |
65 | the PC. A detailed Sync HowTo is available in the | 65 | the PC. A detailed Sync HowTo is available in the |
66 | Help menu of the applications. | 66 | Help menu of the applications. |
67 | 67 | ||
68 | These applications makes it also possible, that you can sync | 68 | These applications makes it also possible, that you can sync |
69 | (or just export the data to) your mobile phone with your | 69 | (or just export the data to) your mobile phone with your |
70 | data of the KDE-desktop calendar/addressbook applications. | 70 | data of the KDE-desktop calendar/addressbook applications. |
71 | This is tested and working for Nokia mobile phones, | 71 | This is tested and working for Nokia mobile phones, |
72 | it may work with others as well. | 72 | it may work with others as well. |
73 | (More info about that: -> Sync HowTo) | 73 | (More info about that: -> Sync HowTo) |
74 | 74 | ||
75 | NOTE: | 75 | NOTE: |
76 | When using SuSE 9.1 you have to update your KDE to 3.3.x | 76 | When using SuSE 9.1 you have to update your KDE to 3.3.x |
77 | and you have to make an online update in SuSE 9.1 to make it | 77 | and you have to make an online update in SuSE 9.1 to make it |
78 | possible to get the infrared connection working, such that | 78 | possible to get the infrared connection working, such that |
79 | you can sync your (Nokia) mobile phone via infrared. | 79 | you can sync your (Nokia) mobile phone via infrared. |
80 | 80 | ||
81 | %files | 81 | %files |
82 | /opt/kde3/share/applnk/PIM-pi/ | 82 | /opt/kde3/share/applnk/PIM-pi/ |
83 | /opt/kdepimpi/ | 83 | /opt/kdepimpi/ |
84 | /usr/lib/libmicro* | 84 | /usr/lib/libmicro* |
@@ -1 +1 @@ | |||
version = "2.1.15"; | version = "2.1.16"; | ||