Leftovers: KDE and Qt
In KDE neon‘s constant quest of raising the quality bar of KDE software and neon itself, I added a new tool to our set of quality assurance tools. CMake Package QA is meant to ensure that find_package() calls on CMake packages provided by config files (e.g. FooConfig.cmake files) do actually work.
A bit later than planned, but here are the 2017 Krita Survey results! We wanted to know a lot of things, like, what kind of hardware and screen resolution are most common, what drawing tablets were most common, and which ones gave most trouble. We had more than 1000 responses! Here’s a short summary, for the full report, head to Krita User Survey Report.
Once 1.5.0 was release I thought the next release would be a small one, it started with a bunch of bug fixes, Simon Wilper made a contribution to Utils::Sql, basically when things get out to production you find bugs, so there were tons of fixes to WSGI module.
The Latin America KDE Summit, LaKademy, just started today in Belo Horizonte, Minas Gerais, Brazil. The country is in the middle of a general strike, which I’m supporting, but the LaKademy couldn’t stop. We’ve been organizing this meeting for a year.
Of course, I inferred it was something to connect a phone and a PC in some way and enabling the swapping of files in between the two devices, but I really did not care much about it. After all, that is what bluetooth is for, right?
Today, I decided to give it a try on PCLOS.
So after a long hiatus I chose the Plasma QuickShare applet (which is sort of the Plasma5 replacement for the old Pastebin Plasmoid) as my point of re-entry into KDE code work. There was after all a deal of itches there I wanted scratched. It’s been quite a bit of fun figuring out the various interesting frameworks QuickShare is connected to at the backend. Anyways, some days ago I got a rudimentary Nextcloud plugin past review and pushed it, which should mean it’ll soon be coming to a 5.10-powered desktop near you :)
On his spare time, Elad Lahav (a kernel developer at BlackBerry) built an experimental Qt-based desktop environment to try and see if he could use QNX as a desktop operating system. And it works!
We recently added a new toy to The Qt Project, and I wanted to give an overview on what it is and how it can be used.
KDevelop, your cross-platform IDE, since version 5.1 has initial OpenCL language support.
Oh Snap – to boldly package where no one has packaged before
One of the great disadvantages of the Linux desktop is its software distribution mechanism. While the overall concept of central software repos works great and has been adapted into powerful Stores in commercial products, deploying and using programs, delivered as packages, is a tricky business. It stems from the wider fragmentation of the distro ecospace, and it essence, it means that if you want to release your product, you must compile it 150 odd ways, not just for different distributions but also for different versions of the same distribution. Naturally, this model scares away the big game.
Recently though, there have been several attempts to make Linux packages more cross-distro and minimize the gap between distributions. The name of the game: Snap, and we’ve tasted this app-container framework before. It is unto Linux what, well, Windows stuff is unto Windows, in a way. Not quite statically compiled stuff, but definitely independent. I had it tested again in Ubuntu 17.04, and it would appear that Snap is getting more and more traction. Let’s have another look.
Kubuntu 17.04 - the next generation
As usual, Kubuntu 17.04 does not give you any surprises. It is stable and reliable. It is reasonably resource-hungry. There are no wonders in this new release. Just a well-rounded distribution for everyday use.
Yes, there are small bugs or inconveniences here and there, but they are not huge and can be easily fixed, replaced or lived with. The biggest of them for me, of course, is the lack of multimedia codecs. You can heal that easily.
KDE vs. GNOME Design Philosophies
The days are gone when the Linux desktop was dominated almost entirely by KDE and GNOME. However, the influence of their design philosophy remains, with KDE favored by a third of users, and many modern desktop alternatives, from GNOME itself to Linux Mint’s Cinnamon and MATE using applications originally designed for GNOME. Broadly speaking, KDE’s design philosopy can be described as completist, and designed for users of all levels of experience, while GNOME’s is minimalist, and aimed particularly at new users — although all levels of users can appreciate GNOME design as well.
By “completist,” I mean that KDE applications try to include every function that could possibly be included in a task. Confusion is limited by the setting of intelligent defaults, but more functions are still visible than most everyday uses require. Perhaps the ultimate example of this design is digiKam, which over the year has calved new windows the way that polar ice caps calve glaciers.
At the opposite end of the spectrum, GNOME applications tend to include only the features for the most common use-cases. This choice makes GNOME apps easy to use, but can leave users stranded if any problems emerge. A typical example is Simple Scan, which is so uncluttered that at first it can almost seem confusing.