|
| This Week... |
|
Kopete 0.12 is released after 10 months of development. Usability fixes in RSIBreak and experiments in amaroK. Common KOffice color management initiative - "pigment" - started. User interface optimisations in Adept package manager. KDE 4 changes: DCOP is finally removed from trunk/. The KDE 4 icon theme, Oxygen, is imported into KDE SVN.
|
After 6 years, DCOP is no more in the development branch of KDE 4. DCOP is an Inter Process Communication (IPC) mechanism, which allows separate applications to interact with each other.
With an effective implementation (such as the one KDE has had for the last 6 years), the holy grail of desktop integration is brought much closer. This fact, however, leads directly to the reason for the replacement of DCOP by D-BUS. The free desktop is now complemented by viable applications that are not based on the KDE platform, and the use of DCOP prevented full integration with those programs. Thiago Macieira, a leading driver of the switch, elaborates:
|
D-BUS brings us better interoperability with many other programs. While DCOP was pretty much restricted to KDE applications (yes, I know there were C bindings, but not many people used it...), D-BUS already comes with bindings for several other major frameworks: glib, Java, Python, Perl, Mono, etc. D-BUS has been designed from the ground up to be an interoperable IPC system and also to replace DCOP when the time came. And so it did.
D-BUS also allows us to better talk to our own system: projects like HAL and Avahi are already being used by many Linux distributions to let normal applications get access to some privileged resources. In time, I also hope the Portland Project to come around and use D-BUS for its IPC needs, thus freeing us from using a special library with its own protocol to do what D-BUS already does.
|
|
Apart from himself, Thiago mentions other developers who have been instrumental in the porting of KDE-Libs to D-BUS: Simon Hausmann, Harald Fernengel, Kévin Ottens, Benjamin Meyer and Roberto Raggi. I believe our thanks, rather than our flames, should go towards these individuals for ensuring the words "highly integrated" are added to the other great adjectives surrounding KDE 4.
|
Preparations for the KDE World Developers Conference 2006, otherwise known as aKademy, have moved up a gear with a "Call For Participation":
|
You're working on innovative and exciting projects related to the "Free Desktop"? You've got something to say to the KDE community? Then this is for you!
The aKademy 2006 conference team is calling for contributors to present their work and vision to the KDE community. This year's conference takes place at Trinity College, Dublin, Republic of Ireland, from September 23rd to September 30th. All presentations will be held during the "KDE Contributors Conference" event on September 23rd and 24th.
Topics of interest include, but are not limited to:- KDE 4 architecture and vision.
- Desktop related hardware and software technologies.
- Innovative human-machine interface design.
- Cool programming tools, patterns and techniques.
- Applications written for the K Desktop Environment.
- Advancements in l10n and i18n.
- Quality Assurance in Open Source projects.
- Legal, social, philosophical or promotional matters related to KDE.
- Desktop software standards, usability and accessibility.
- Performance analysis and improvements.
|
|
This means that developers who would like to make a formal presentation have until June 30th (the end of this month!) to submit a 300 word description of their proposed talk. For everyone else who would like to enjoy these presentations and other activities, actual registration for attendance should open within the next few days.
|
To complement the fundemental changes shaping the next major version of KOffice - version 2.0, which will be based on Qt4 - such as the Flake graphical object library, Casper Boemann announces the start of his work to bring colour management availability to all applications of the office suite. Historically, colour management has only been available in Krita, but access to these features across the board should bring noticable improvements to all documents created. To best explain why colour management is important, some words from Casper:
|
Color management is a very important feature in a professional setting like printing and web design. To understand what it is all about think of a webdesigner. She sits at her own computer and creates a page with colors that look stunning on her monitor. Unfortunately no two monitors show colors in the same way, so without color mangement it might look quite different when someone else views it on another monitor.
The way color management ensures that colors look the same on both (and indeed every) monitor is through the use of profiles. It's possible to measure the profile of a monitor. So the color management software just has to tweak the rgb triplets so that the visual effect is the same.
|
|
Jos van den Oever writes a brief update on a week of progress with "kitten", his personal indexer project:
|
- expanded number of backends to four: hyperestraier, clucene, sqlite and xapian. hyperestraier is recommended because of it's speed and small index.
- moved in svn to /trunk/playground/base/kitten so check out with:
svn co svn://anonsvn.kde.org/home/kde/trunk/playground/base/kitten - added support for choosing the backend at runtime.
- abstracted the Query object to simplify querying over different backends.
|
|
|
| Statistics |
|
Commits: |
2284
by 203
developers, 5465
lines modified, 2596
new files. |
|
Open Bugs:
|
12578
|
|
Open Wishes:
|
11002
|
|
Bugs Opened:
|
345 in the last 7 days. |
|
Bugs Closed:
|
253 in the last 7 days. |
|
|
Commit Summary |
|
Module
|
Commits
|
|
/trunk/www |
|
|
/trunk/KDE |
|
|
/branches/work |
|
|
/trunk/extragear |
|
|
/trunk/l10n |
|
|
/trunk/playground |
|
|
/trunk/koffice |
|
|
/branches/stable |
|
|
/branches/KDE |
|
|
/branches/koffice |
|
|
|
Lines
|
Developer
|
Commits
|
|
|
Laurent Montel
|
|
|
|
David Faure
|
|
|
|
Dirk Mueller
|
|
|
|
Matthias Kretz
|
|
|
|
Ludovic Grossard
|
|
|
|
Gilles Caulier
|
|
|
|
Pino Toscano
|
|
|
|
Thiago Macieira
|
|
|
|
Stephan Kulow
|
|
|
|
George Staikos
|
|
|
|
|
Internationalisation (i18n) Status
|
|
|
Bug Killers and Buzz |
|
Bug Killer
|
Number Of Bugs Closed
|
|
Chris Howells
|
|
|
Thiago Macieira
|
|
|
Mark Kretschmann
|
|
|
Sebastian Trueg
|
|
|
Tom Albers
|
|
|
Joris Guisson
|
|
|
Jaison Lee
|
|
|
Aaron J. Seigo
|
|
|
Gilles Caulier
|
|
|
Luboš Luňák
|
|
|
|
Program |
Buzz |
|
amaroK |
|
3136 |
|
|
Kopete |
|
1273 |
|
|
K3B |
|
|
Kate |
|
|
KMail |
|
|
SuperKaramba |
|
|
KDevelop |
|
|
Kontact |
|
|
Kicker |
|
|
Quanta |
|
|
|
Person |
Buzz |
|
Waldo Bastian
|
|
336
|
|
|
George Staikos
|
|
312
|
|
|
Boudewijn Rempt
|
|
296
|
|
|
Aaron Seigo
|
|
293
|
|
|
David Faure
|
|
280
|
|
|
Cornelius Schumacher
|
|
276
|
|
|
Anne-Marie Mahfouf
|
|
275
|
|
|
John Tapsell
|
|
266
|
|
|
Jonathan Riddell
|
|
258
|
|
|
Stephan Kulow
|
|
257
|
|
|
|
|
|
| Contents |
|
|
Bug Fixes |
Features |
Optimise |
Security |
Other |
|
Accessibility |
|
|
|
|
|
|
Development Tools |
|
|
|
|
|
|
Educational |
|
|
|
|
|
|
Graphics |
|
|
|
|
|
|
KDE-Base |
|
|
|
|
|
|
KDE-PIM |
|
|
|
|
|
|
Office |
|
|
|
|
|
|
Konqueror |
|
|
|
|
|
|
Multimedia |
|
|
|
|
|
|
Networking Tools |
|
|
|
|
|
|
User Interface |
|
|
|
|
|
|
Utilities |
|
|
|
|
|
|
Games |
|
|
|
|
|
|
Other |
|
|
|
|
|
|
|
Bug Fixes |
|
Development Tools |
|
Thiago Macieira committed changes in /trunk/kdesupport/qt-dbus:
|
Here's what happens when you start using code that had never been used before: it doesn't work.
Don't clear the list of watchers, or we'll never get any messages in D-BUS.
Also, move the QDBusConnectionPrivate::timerEvent into the qdbusintegrator.cpp file and make a queued call to doDispatch after sending a message (we may have got something to read). |
|
|
|
|
|
|
David Nolden committed changes in /branches/kdevelop/3.4/languages/cpp:
|
no more code-completion within comments! Also fix a problem with slotTextHint() where the slot was not disconnected correctly, and the text-hint got slower and slower because slotTextHint was called increasingly often for each hint. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|