- Fixed problems setting up buttons in panel
- Added Desktop Sharing
- Added File Associations
- Adjusted workflow
- Support for renaming profiles / profile directories
This Week...
Kopete Groupwise support ready for testing. Digikam adds oil-painting and charcoal drawing effect plugins. Two new kioslaves; kio-trash and kfiledevice for disk size and usage. Kexi now supports subforms. Work started on a common multimedia interface to various backends.
As you can see by the rather large list of bugfixes and new features, this has been an eventful week. KDE developers are gathered at the aKademy for conferences, talks, hacking sessions, socializing and commiseration afterwards. These meets allow for decisions to be made, future directions to be decided. No doubt announcements will be made in the coming weeks, but watching the code commits gives a hint of what is to come.
There is a general consensus among KDE developers that aRts sucks. It is unmaintained and possibly unmaintainable. So what multimedia backend should KDE support? GStreamer? NMM? MAS? All three were discussed last weekend at aKademy (video and audio archives here). Each has advantages and disadvantages. Which framework should KDE use? In the best tradition of, well, everything, the best choice iswhen one can avoid a decision. So developers started building a backend called kdemm which is described by Matthias Kretz as "A common interface to multimedia functions that are implemented in exchangeable backends".
We are all curious about the next version of KDE. Will it be 4.0, meaning based on QT 4, in other words sometime towards the end of next year? Or will another 3 point release? Here is the 3.4 feature plan which so far is simply all the unfinished 3.3 stuff moved forward. No doubt there will be more news on this front in the near future.
There is a general consensus among KDE developers that aRts sucks. It is unmaintained and possibly unmaintainable. So what multimedia backend should KDE support? GStreamer? NMM? MAS? All three were discussed last weekend at aKademy (video and audio archives here). Each has advantages and disadvantages. Which framework should KDE use? In the best tradition of, well, everything, the best choice iswhen one can avoid a decision. So developers started building a backend called kdemm which is described by Matthias Kretz as "A common interface to multimedia functions that are implemented in exchangeable backends".
We are all curious about the next version of KDE. Will it be 4.0, meaning based on QT 4, in other words sometime towards the end of next year? Or will another 3 point release? Here is the 3.4 feature plan which so far is simply all the unfinished 3.3 stuff moved forward. No doubt there will be more news on this front in the near future.
Statistics
Commits | 2497 by 202 developers, 277054 lines modified, 2618 new files |
Open Bugs | 7208 |
Open Wishes | 6878 |
Bugs Opened | 454 in the last 7 days |
Bugs Closed | 464 in the last 7 days |
Commit Summary
Module | Commits |
kde-i18n |
626
|
kdepim |
224
|
www |
205
|
kdeextragear-2 |
186
|
kdenonbeta |
174
|
koffice |
153
|
kdelibs |
149
|
kdebase |
99
|
kdeextragear-1 |
96
|
kdevelop |
65
|
Lines | Developer | Commits |
16114
|
Erik Kj |
147
|
1451
|
Stephan Binner |
72
|
5781
|
Stephan Kulow |
71
|
1984
|
Jarosław Staniek |
61
|
1938
|
Reinhold Kainhofer |
55
|
734
|
David Faure |
52
|
7261
|
Frans Englich |
50
|
1325
|
Tobias Koenig |
49
|
648
|
İsmail Dönmez |
49
|
3956
|
Logi Ragnarsson |
45
|
Internationalization (i18n) Status
Language | Percentage Complete |
Portuguese (pt) |
99.6%
|
Swedish (sv) |
98.86%
|
British English (en_GB) |
98.68%
|
Danish (da) |
98.68%
|
Estonian (et) |
98.3%
|
Spanish (es) |
96.16%
|
Dutch (nl) |
95.56%
|
Brazilian Portuguese (pt_BR) |
94.07%
|
Italian (it) |
93.7%
|
Tamil (ta) |
93.19%
|
Bug Killers
No commits found