A nice feature coming to KDE Plasma 5.7 is support for logging into an online account from the login manager to have your Plasma configuration synced from the remote server. Initially this work is focused around supporting ownCloud. If supplying your username, password, and ownCloud provider to the Plasma 5.7 log-in screen, you'll have all of your data synced locally. This will include Plasma's look and feel, ownCloud hosted files, email data, contacts, and calendar.
GNOME 3.20 is the first major update to the GNOME desktop environment in 2016, officially becoming generally available on March 23—and since that date it has been slowly trickling into the repositories of Linux distributions. GNOME 3.20 is code-named Delhi in honor of the GNOME.Asia event that will be held in Delhi, India, April 21-24. The new GNOME release is the first since GNOME 3.18 in September 2015, and it provides incremental improvements. An overarching update across multiple applications in GNOME 3.20 are new shortcut screens that provide users with a simple list of keyboard shortcuts to perform common actions in a given application. As was the case with GNOME 3.18, the File utility in GNOME 3.20 benefits from usability improvements. This time, the improvements are around searching and finding files on the system. The Web application is also improved, with improved session restore capabilities. In this slide show, eWEEK takes a look at the key features of the GNOME 3.20 desktop update.
My previous post, as many have quickly realized, was an April Fool’s joke, sorry. But it will not be entirely false: the only sure thing is that something as complex won’t be released for the 5.7. And what makes it so complex is the involvement of the login manager (SDDM). In fact, as many pointed out around the web, there would be security risks. After all it wanted to be a joke.
By the way the integration with Internet services and sync of user’s data was and is a topic discussed in Plasma. Today, because of this joke, we at VDG discussed about this feature. Here there are some conclusions/ideas:
As QtWebKit will be remove from official Qt package I decided some months ago to evaluate QtWebEngine.
For sure QtWebEngine < 5.6 was too limited. But I started to use it. I evaluated QtWebEngine 5.5 but some features were missing (as possibility to block request or use custom scheme url).
I started to focus on Akregator as it still used khtml, I migrated it to QtWebKit and after that to QtWebEngine. (For 16.04 there is a experimental option to activate compilation).
While Qt 5.6 was just released after being delayed by months, Qt 5.7 was supposed to be a quick follow-on release but it too is already seeing delays.
Qt 5.7 went into alpha while Qt 5.6 was still being prepared for release, but now the Qt 5.7 beta is going to be delayed by an unknown amount of time.
Today, March 30, 2016, KDE, through Thomas Pfeiffer, has proudly announced a new framework for developers who want to build cross-platform Qt-based applications.
I previously reported that, although WebKitGTK+ releases regular upstream security updates, most Linux distributions are not taking the updates. At the time, only Arch Linux and Fedora were reliably releasing our security updates. So I’m quite pleased that openSUSE recently released a WebKitGTK+ security update, and then Mageia did too. Gentoo currently has an update in the works. It remains to be seen if these distros regularly follow up on updates (expect a follow-up post on this in a few months), but, optimistically, you now have several independent distros to choose from to get an updated version WebKitGTK+, plus any distros that regularly receive updates directly from these distros.
GUADEC 2016 will be held for the first time in Karlsruhe, Germany. The conference will be held on August 12th-14th, with a day of workshops beforehand, and 3 days of BoFs and hackfests after.
KDE has a long tradition of providing user interface components beyond the basics that are offered in Qt itself. With KDE Frameworks 5, these have become more easily available for Qt developers who are not part of KDE. Now, with KDE's focus expanding beyond desktop and laptop computers into the mobile and embedded sector, our QWidgets-based components alone are not sufficient anymore. In order to allow developers to easily create Qt-based applications that run on any major mobile or desktop operating system (including our very own existing Plasma Desktop and upcoming Plasma Mobile, of course), we have created a framework that extends the touch-friendly Qt Quick Controls: Welcome Kirigami UI!
The latest version of digiKam has been added to the unofficial ports tree in area51. The unofficial ports tree is where the KDE-FreeBSD team works on ports in preparation for their inclusion into the official ports tree. The trunk of that repository is basically “what’s next” for the official ports tree from our point of view. There are other branches: mostly plasma5, for the upcoming (from a FreeBSD perspective, at least) KDE Frameworks 5 and Plasma 5; qt5.6 for testing the recently-released Qt 5.6. Official ports will remain Qt 5.5 for the time being.
Manjaro 15.12 KDE 64-bit in Live session felt very snappy and fast. I had no issues with the system performance.
However, there were still some issues that I drew attention to in the paragraphs above.
I would like to say that if I had a choice between the KDE and Xfce editions of Manjaro operating system, the latter would still be my preference.
Over the years, I've found that trying to select the best Linux desktop environment is almost an impossible task. There are oodles of considerations, ranging from level of user experience to individual user preferences. Despite these challenges, there are some solid considerations we can evaluate individually.
In this article, I'm going to hit on a number of Linux desktop environments. I'll look at what about them is appealing and why folks are inclined to think of them as “best” over other alternatives.