You don’t have to remove the KDE 5 packages in order to get logged into your familiar KDE 4 desktop by the way – just choose the appropriate Desktop Environment. As I said, the two environments don’t bite.
One thing you will notice, is how fast the new desktop is. The Plasma Desktop in KDE 5 uses an all-new, fully hardware-accelerated graphics stack on top of Qt5 and the Frameworks5 libraries, and the effect is amazing. Resource usage is still high but the reason for that is known: it is caused by a design issue in KWin and that is currently being worked on.
KDE 5 has been my default desktop for the past week (using Plasma 5.0.0 package), and I hope that the update to Plasma 5.0.1 will fix a couple of pesky bugs.
KDE has today made the first update to KDE Frameworks 5. Frameworks are our addon libraries for Qt applications which provide numberous useful features using peer reviewed APIs and regular monthly updates. This release has 60 different frameworks adding features from Zip file support to Audio file previews, for a full list see KDE's Qt library archive website Inqlude. In this release KAuth gets a backend so you can again add features which require root access, KWallet gets a migration system from its KDELibs 4 version and support has been added for AppStream files.
When we were building towards 5.0, we made the choice to focus all the effort on the core, and not release plasma-addons. It would have been simply too much work and quality of the core would have suffered.
The intention was to start bringing them back from 5.1, which will be in approximately 2 months from now.
The amount of stuff in plasma addons is huge.
As the adoption of Qt is increasing in commercial as well as Open Source projects the company behind the project, Digia, has decided to spin Qt unit as a new company.
Digia has been facing a resource challenge with Qt as 75% of the contribution comes from Digia employees. Qt has dual presence one at qt.digia.com and one at qt.project.com and these two sites or two entities have drifted apart instead of coming closer. Now what is the difference between the two? Same as with any open source project and commercial product. qt.digia.com is all about commercial offering whereas qr-project is all about the community.
As usual, we have worked hard to close your reported issues since the previous stable release 4.1.0. A list of the issues closed in digiKam 4.2.0 is available through the KDE Bugtracking System.
As part of the core Plasma team I have spent a long time helping in the migration to make everything QtQuick2.0 based, making sure we get the most out of the OpenGL backing.
This weekend I wanted to make some sort of demo which shows the power of this in the form of an interactive wallpaper.
I’ve wrote a simple plugin for KTextEdit (Kate, KDevelop, and other programs that uses the KDE text editor component) that provides code completion for Go, by using gocode as backend.
Besides these application the VDG is also working with developers (or without) on an image viewer and a video player. Besides that we want to make slight improvements to key areas of Plasma 5 e.g. the system tray. As you can see there’s still much to do, but we’re pleased with the progress made so far.
Every backer who pledged 25 euros or more had a chance to vote for their favorite feature -- and the now the votes are in and have been tallied up! Here are the twelve features that Dmitry will be working on for Krita 2.9:
David Edmundson and I have been working hard the last weeks. It’s not that we don’t usually work hard, but this time I’m really excited about it.
A bit of context: in Plasma an important part of the system drawing is painting frames (others are icons, images and the like). Those are in general the elements that are specified in the Plasma themes. These will be buttons, dialog backgrounds, line edit decorations, etc.
In one week the Randa Meetings 2014 will start and this is possible because of you. You supported us (and can still support us and thanks to you we will be able to improve your beloved KDE software even more. So it's time to give you something new. Here is another interview with one of the persons who will be participating in this year's meetings (and participated since the start in 2009). And watch out for some other interviews to come in the next days and weeks.
July 31, 2014. Today KDE released the Release Candidate of the new versions of Applications and Development Platform. With API, dependency and feature freezes in place, the KDE team's focus is now on fixing bugs and further polishing.
With the large number of changes, the 4.14 releases need a thorough testing in order to maintain and improve the quality and user experience. Actual users are critical to maintaining high KDE quality, because developers simply cannot test every possible configuration. We're counting on you to help find bugs early so they can be squashed before the final release. Please consider joining the 4.14 team by installing the release candidate and reporting any bugs.