Here is my thinking (which may just be faulty) —
- I find it distasteful that when you go to configure a software the first thing you see is how to disable it. I understand that you may dis-agree, but that is my opinion.
As with many jokes or lies, there was a kernel of truth in it! While we certainly do not want to faithfully recreate the experience of KDE 2 (or even KDE 3) with Plasma Next, Jens and I indeed have been thinking about offering users the choice between a set of pre-configured setups we’d like to call Experiences. Those would include things like Panel configurations, Plasmoids, application menu positions (in the window in a Panel in the window’s title bar / …), Plasma theme, widget theme, window decoration theme, cursor theme or the selection of KWin effects (like desktop/task switcher, animations, etc.). Part of the groundwork for this are the Plasma Look and Feel packages which go a great length in the visual department, but our idea goes way beyond that.ℹ sessellift.wordpress.com
The OSD use case is illuminating. Future versions of Plasma will provide a DBus service that can be used for simple OSD needs, like changing volume in an application. I expect in time the service will grow features to support more sophisticated OSD display patterns, as this will not only increase desktop integration but provide a way to work around security restrictions display systems like Wayland and Mir enforce.ℹ aseigo.blogspot.com
KDE Telepathy 0.8 is out
During the 0.8 development cycle we focused on bug fixing rather than implementing lots of new features. The biggest changes from 0.7 are all under the hood. We rewrote the metacontacts library, KPeople, almost completely from scratch and made it independent from Nepomuk, which should bring more performance, reliability and stability to the contact list and (meta)contacts management.
In this week's KDE Commit-Digest:
_Akonadi speeds up_ appending new items