This week in Usability & Productivity, part 19

This week we announced a beta of the upcoming KDE Plasma 5.13 release, and so far the internet seems pretty excited about it. 🙂 But we’re nowhere near done, and here’s another week of Usability and Productivity enhancements to highlight:

New Features


UI Polish & Improvement

See all the names of people who worked hard to make the computing world a better place? That could be you next week! Getting involved isn’t all that tough, and there’s lots of support available. Give it a try today! It’s easy and fun and important.

If my efforts to perform, guide, and document this work seem useful and you’d like to see more of them, then consider becoming a patron on Patreon, LiberaPay, or PayPal.

Become a patron Donate using Liberapay donate with PayPal


16 thoughts on “This week in Usability & Productivity, part 19

  1. Hi!, nice to read in this series of posts how the interface is evolving.

    I have 1 question and 1 suggestion:

    I’m using the latest Ubuntu who use Gnome, it is possible try Plasma without reinstall the OS?

    For a next phase, I think would be useful start thinking on Plasma as a component based design system, what do you think?

    Separate the system in styles and components can be useful to maintain consistency trough the whole interface, also good for documentation, see this examples

    At the moment I’m only find this documentation about Plasma: (let me know if are other)

    Hope can help!


    1. For the most part, KDE Software is very well modularized. This was a big goal of version 5 (e.g. KDE Frameworks 5 & Plasma 5). It’s generally not recommended to install multiple desktop environments alongside one another, as there are usually conflicts. The best way to try KDE Plasma without installing it is to use a Live USB disk for a KDE-using Linux distro, such as Kubuntu, OpenSUSE, or KDE Neon.


  2. Awesome work! I was just thinking how hard is it to make shadow smaller for inactive windows, because now it is exactly the same. And i see that as an issue, since every other known desktop environment reduces the intensity for inactive window shadows.


  3. The pacman update for Discover is a really nice improvement. I always used discover as a merely update notifier, because I couldn’t see in a simple way what’s happening. I had to open a terminal to follow the log file… and at that point, it was easier to just launch pacman -Syu.


    1. Yes, this came out of a conversation with various Arch users and the Arch KDE packager. It turned out that a major objection was the lack of a log viewer, because Arch’s package management approach was designed with the requirement that users to read the log.


      1. I love the update log output from pacman. It’s so clear and well put. Discover felt messy and weird without it (parallel downloads or no clear graphical sign when many packages were downloaded at the same time so it took a while till you saw even 1% in some random package). It’s awesome that discover starts to feel like in a place with the system now.
        Change of single/double click is a good one as well. Previous place was counter intuitive.

        Krunner being case sensitive may not be that good. Do I understand it right, that wen searching, let’s say firefox, I have to start typing Fi… and not fi because krunner won’t output results? I would rather have it as option that I can turn it on/off,


        1. Actually it’s the opposite: KRunner searches are now case INsensitive, so you *don’t* have to type “Firefox” have Firefox be the top entry.


  4. It’s great KDE is changing so much and so fast. It’s getting better and better every week. But (and there is always a but), is any work done on Kdenlive? On the bugreport page I see a very long list of bugs and it seems they are not handled, although I am probably wrong here. This morning I helped somebody on the Manjaro forums who had problems with version 18.04.1: colorclips all turned white instead of having the color as intended. Managed to find an older snapimage and now he can continue to do his job.
    Please don’t only create new flashy things, also make programs work as intended and above all bugfree.


    1. Kdelive is actively developed. Please file bugs for any issues you encounter. There are a lot of open bugs because it’s a huge project!


  5. (previously attempting posting but got stuck “awaiting moderation”: trying again with spaces around / in file paths)

    As a new Plasma user, I am struggling with how to use KRunner more effectively. I am coming from Gnome-Do and later Synapse (which I am still using in Plasma until I can see if KRunner can replace it).

    My main workflow is to open a containing folder in dolphin based on typing part of the folder name. So in Synapse by typing “pac” it would prompt for / data / 1-work / dev / packages and hitting enter would open a dolphin folder to this “packages” location.

    Am I missing something for KRunner to be able to do this? It seems to only be able to “find” folders by using the FQDN, so I need to type / data / 1-work / dev / pac then it would find.

    In short, I *think* Baloo is indexing the filenames (well, maybe it only indexes files NOT folders?), but KRunner doesn’t allow a sort of “fuzzy folder search”?


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s