| jeremy |
06-27-2014 11:07 AM |
Where KDE is going - Part 1
Quote:
This article explores where the KDE community currently stands and where it is going. Frameworks, Plasma, KDE e.V., Qt5, KDE Free Qt Foundation, QtAddons - you heard some of these terms and want to know what all the fuss is about? A set of articles on the Dot aims to bring some clarity in the changes and constants of the KDE community in 2014 and further. This is the first article, diving into the technical side of things: Plasma, applications and libraries.
Plasma by KDE
Plasma was conceived as the next generation of KDE's desktop technology. When its architecture was drafted in 2006 and 2007, the goal of the developers was to build a modular base suitable for multiple different user interfaces. It is easy to see this as an obvious goal in a world with high resolution displays, tablets, mobile phones, media centers and so on. But as argued here, until today, KDE technology is unique in its ability to converge the different form factors at a code level. Others are still either attempting to build one interface for a wide variety of devices, looking for a middle ground or have realized that user interface convergence is a futile exercise and created separate interfaces.
Plasma 5
Plasma took some time to mature, in part due to its ambitious design, in part because the technologies it built upon were not mature enough for the needs of Plasma. This is still somewhat of a problem today, and the 4.x series has workarounds to deal with the deficiencies in the platforms below it.
This is where the next generation of Plasma technology comes in. Conveniently named Plasma 5, it will bring pixel-perfect design and super smooth performance thanks to the QML and Qt 5 technologies and fully hardware accelerated display rendering. High DPI support and the ability to work with Wayland (Linux's next generation display server) are planned as well, but neither are expected to be fully finished with the first release.
With Plasma 5 the team can start working on bringing seamless switching of work-spaces when moving from device to device. For example, plugging a keyboard and mouse into a tablet can trigger Plasma to transform its tablet-and-touch optimized UI into the desktop interface. And the applications, being notified of the change, can follow adapting to the new form factor. The current Plasma technology already can hint to applications which QML/ Javascript/ graphics files fit the current form factor and is already being used in Plasma Active, the tablet-optimized workspace of Plasma. None of this requires logging out-and-in – you can just continue working with the document you were working in or keep reading that web site!
|
More at dot KDE...
What do LQ members think of where KDE is going?
--jeremy |
