The Qt 5.4 feature freeze is set to go into effect on 8 August with already there being a large number of changes for this next major Qt5 tool-kit release.
Heikkinen Jani of Digia sent out a reminder this morning that the 5.4 feature freeze is effective beginning 8 August. The Qt 5.4 code will be branched from Qt's "dev" branch on 11 August.
The WebODF library webodf.js comes with a rich API and lots of abstraction layers to allow adaption to different backends and enviroments. There is an increasing number of software using WebODF, some of that listed here.
From the fourth to the sixth of July, the Calligra team got together in sunny Deventer (Netherlands) for the yearly developer sprint at the same location as the last Krita sprint. Apart from seeing the sights and having our group photo in front of one of the main attractions of this quaint old Dutch town in the province of Overijssel, namely the cheese shop (and much cheese was taken home by the Calligra hackers, as well as stroopwafels from the Saturday market) we spent our time planning the future of Calligra and doing some healthy hacking and bug fixing!
Before heading into the weekend I thought about writing a small update about the KDecoration2 status. Since my last blog post I started integrating KDecoration2 into KWin. This was partially easier and partially more difficult than anticipated. Especially ripping out the old decoration code is rather complex. There are quite some design differences which make the transition complex and especially values inside KWin core are using enums defined in the decoration API – e.g. the maximized state is kept as a KDecorationDefines::MaximizedMode. This will need further work to move the enums and so at the moment the old decoration library is still compiled although the library is no longer in use.
With the Plasma 5.0 release out the door, we can lift our heads a bit and look forward, instead of just looking at what’s directly ahead of us, and make that work by fixing bug after bug. One of the important topics which we have (kind of) excluded from Plasma’s recent 5.0 release is support for Wayland. The reason is that much of the work that has gone into renovating our graphics stack was also needed in preparation for Wayland support in Plasma. In order to support Wayland systems properly, we needed to lift the software stack to Qt5, make X11 dependencies in our underlying libraries, Frameworks 5 optional. This part is pretty much done. We now need to ready support for non-X11 systems in our workspace components, the window manager and compositor, and the workspace shell.
The K Desktop Environment (KDE) is among the most popular and long-lived open-source desktop environments for Linux and Unix users. Dating back to 1996, KDE is one of the earliest Linux desktop environments, predating the GNOME desktop environment, which got started in 1999. KDE has gone through multiple evolutions, the most recent being KDE Plasma 5, which was officially released on July 15. With the Plasma 5 desktop, KDE is providing users with both under-the-hood enhancements and user-facing improvements. Plasma 5 is powered by the open-source Qt 5 cross-platform user interface framework. Hardware acceleration for graphics is now supported with the OpenGL graphics API. With Qt 5 and OpenGL, Plasma 5 is able to provide users with not only improved graphics performance, but also a more fluid user experience. Plus, the new Kickoff application launcher enables users to rapidly find and access applications and content on a system. KDE as a desktop environment is available on multiple Linux distributions, including Ubuntu, KaOS and openSUSE. In this slide show, eWEEK examines some of the key features of KDE Plasma 5.