Here in the KDE office in Barcelona some people spend their time on purely upstream KDE projects and some of us are primarily interested in making distros work which mean our users can get all the stuff we make. I've been asked why we don't just automate the packaging and go and do more productive things. One view of making on a distro like Kubuntu is that its just a way to package up the hard work done by others to take all the credit. I don't deny that, but there's quite a lot to the packaging of all that hard work, for a start there's a lot of it these days.
KDE is now getting into the swing of releases numbered 5. Today we add Plasma 5's first bugfix update. The release features KDE's flagship desktop project as well as the base software needed to keep your computer running. Plasma will have feature releases every three months and bugfix releases in the months in between.
This screenshot shows the QML/JS KDevelop plugin working as usual, highlighting declarations and uses, finding types, and displaying nice tool-tips. The code-completion also works even if it is not visible on the screenshot. What is interesting is the look of KDevelop: do you see the flatter theme? The colors that are a bit different than usual? This difference is appearance comes from the fact that this is not the usual KDevelop, this is KDevelop 5, based on Qt5 and on the shiny new KDE Frameworks 5.
Also note that only Python 3 is supported. It doesn't make sense to support legacy Python versions like 2, especially when developers need to do a port anyway from PyKDE4 to PyKDE5.
Another important reason is that it costs more time and effort to support more configurations. It is no secret to anyone who has followed PyKDE4 development and support just a little bit, will have noticed that my time for KDE is very limited. The situation isn't likely to improve, in fact in a couple months it should get worse if all goes to plan. I see that some people have stepped in to fill the void and fix some of the build and installation problems they have encountered (hi Luca!). This is great and I encourage people to get involved where possible. The hardest part is getting a working dev environment set up, deep C++ knowledge isn't really needed (I certainly don't have deep C++ knowledge!).
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.