This week in Usability & Productivity, part 47

This week in Usability & Productivity we did a lot of work on our Plasma 5.12 long-term support release and performance improvements for KIO and Baloo (many of which are not individually significant enough to be mentioned here, but will add up to some great improvements over time). Lots of nice bugfixes and new features snuck in, too.

New Features

Bugfixes & Performance Improvements

User Interface Improvements

Next week, your name could be in this list! Not sure how? Just ask! I’ve helped mentor a number of new contributors recently and I’d love to help you, too! You can also check out https://community.kde.org/Get_Involved, and find out how you can help be a part of something that really matters. You don’t have to already be a programmer. I wasn’t when I got started. Try it, you’ll like it! We don’t bite!

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. Also consider making a donation to the KDE e.V. foundation.

17 thoughts on “This week in Usability & Productivity, part 47

    1. Thanks, It’s good to know it’s appreciated!

      A daily blog would require a whole team, I think. Even just putting this together every week takes up a significant amount of time. It’s not a trivial thing. 🙂

      Liked by 1 person

  1. Awesome!

    Not sure I understand this one thou:
    “Comboboxes in QML and Kirigami apps and Plasma now open on click, not on click-and-release”.

    I’m used to behavior that EVERY CLICK works after release, never before. This saved me from doing many serious mistakes where I accidentally clicked something but immediately realized it, so I held the click, moved the cursor over “not allowed” area and then released it, so there was no effect, which was often life-saving.

    This works on Windows and Linux everywhere, at least as far I could notice. Changing it to opposite doesn’t sound like safe or good idea. Working on release is a most common mechanism on clicks. This also works in a browser (easy to test, click on any link – nothing happens, release button, a link is activated) so it’s the natural way of behavior and also a safeguard.

    Maybe there is some specific need or reason for using it another way on kirigami? I’m just curious, what is the reason behind it.

    Like

    1. The comboboxes in QWidgets based apps (Dolphin etc.) already have this behaviour. This change merely aligns the behaviour of QML based ones (Discover etc.) with it.

      Just opening a combobox doesn’t trigger any action, so even if you do it by mistake there is no harm done

      Like

    2. I don’t think it’s a problem here because nothing different from what is already selected in the combobox will be selected until you release on a different option. This change just makes QML/Kirigami comboboxes more consistent and faster to work with. You can still release off to the side to avoid selecting a different option.

      Like

    3. The change simply makes QML and Kirigami apps consistent with how it’s always been for QWidgets apps: comboboxes are *supposed* to open on click on Linux. It’s a productivity feature. You can click, drag down to the item, and release all in one gesture. It’s the same way menus work. macOS does this too.

      Once you learn about this and get used to doing it, the clunky Windows workflow becomes unbearable.

      Liked by 1 person

  2. Because of these blog posts, for the past couple months i have been in love with Plasma. I am kind of curious though, how are the framework updates handled? Are they released whenever they are ready, or are they only released in the next major plasma update? I still don’t have the icon fixes from the last frameworks update in solus or kubuntu backports?

    Like

      1. Thanks. That’s really weird… I have 5.52 but the icons are no different… Yet in KDE Neon Git they are the new emblems and icons

        Like

        1. Run rm ~/.cache/icons*. Does that fix the problem? If not, it sounds like a distro packaging issue. If so, please open a bug report on bugs.kde.org, since they should be getting updated automatically without needing for you to do that.

          Like

  3. This is always a very interesting read. Before discovering this site all these new features would have probably stayed under the radar until I accidentally found them.

    Like

Leave a Reply

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

WordPress.com Logo

You are commenting using your WordPress.com 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