 Welcome to this episode of KDE News where I talk about some of the features that KDE is implementing and actually how they are implemented. So we can actually learn a bit how it works behind the scenes and if you want, eventually maybe you can start working on some of these things too. Now, the major features of this week are like the dressers but I've done an entire video about them. So maybe it's only fair to do some smaller stuff that we can actually see really easily how they are implemented so we learn the most out of them. But before we get into that, as always, thank you to the sponsor of this video, which is Nobody. I'm doing this in my free time and if you want to help me do this kind of things like actually develop for KDE but I also do like my own life, I write poetry, this kind of things I'm allowed to do them because there are people who sustain me and you've seen the videos on names on the screen, patterns, donations. So if you manage to, if you have the possibility, it would be amazing to receive a little donation but of course that's up to you and let's actually get to the video. I choose this four, one, two, three, four. So the first one is the task manager. This one is about wallpapers. This one is just a commit and it's about the key runner and this one is about the battery monitor. Let's do them. This one, increased spacing in tablet mode. I think it looks pretty good. So the idea is this is a ThinkPad that supports tablet mode and so when you actually rotate the computer enough it actually enters tablet mode and the idea that is being implemented on since quite some time ago at this point, Nate is doing lots of great work about this, he is making the margin of the buttons and the buttons bigger when you're in tablet mode but only when in tablet mode so it's easier to use. My personal criticism to this partially is that we cannot always know if touch input is used in tablet mode. I would prefer a UI to be always usable with touch regardless of tablet mode but surely if we know for sure that the user is going to use touch it's better to make that button bigger. So in this case we're talking about the task manager and you can easily see that when you switch from one mode to another the size of the buttons changes. So that's the point. This changes the config slightly. Before we add this spacing between icons small, normal, large and when we have tablet mode it's automatically set to large. So you can actually manually configure it to be always large if you want but also small if you prefer some compact stuff. And about this, there is a lot of talk about going on in KDE about having a more general option for information density because we observe that some people really prefer to have as little margin as possible whereas a lot of people would like all of the elements to be, well, touch usable for sure but also maybe also preter some people prefer it that way I personally do with more margin around them. But even just in the task manager an option to change the spacing and making sure that when you're in tablet mode there is more spacing. How is this implemented? Well, first of all, we add the label that we've just seen that says Android set of, sorry automatically set to large when in tablet mode this one is the text that we've before this one, the one I was reading under a set of radio buttons when the tablet mode is on it's actually the description on how this string is used. As an example, this could be useful in translations to actually know what is the context of this sentence. If you get to translate a string without any context it's pretty hard to understand it. And this is visible. Let's zoom in. Thank you. Good club. So beautiful. This is only visible when Corogami settings table tablet mode. So when you are in tablet mode Corogami settings tablet mode is Corogami abstracting over tablet mode so that you don't have all application to implement their own thing to read if we're in tablet mode or not. It's just handled, handled, handled by Corogami. Then of course we have the buttons and there's no longer a huge button but there is a big one which is just above here, large and we can see that if we are not in tablet mode this is enabled as in you can actually select large if you are not in tablet mode and this also applies to normal and small. Right now we're talking about the settings part of it and it is only checked. It is only pressed if we are not in tablet mode same for normal and here checked becomes here if we have selected it or we are in tablet mode. So this is the settings part of it. Now, where do we actually read the settings were? Well, this one was it. These options of small, medium, large spacings were actually implemented already even before this patch and they are read in the task manager item QML to actually set the margin between to the left and to the right of each icon in the task manager. The only other thing we change in this particular patch in the layout.js that we see that the spacing adjustment we are here saying let's check the spacing between the icons but if we are in tablet mode then it's always three. What's three? Well, we've got one which is small to medium, three large. So three is large. Same thing here. Icon spacing only if we are not in tablet mode. Otherwise, always be regardless of what the user decided. And that's the whole merge request. That's it. So it's really easy to understand some merge requests. Next one, I'm not going to go through the code but I thought it was pretty interesting as a concept and this one was actually, let's say it rejected from the reviewers as it shouldn't be part of KD Plasma but we'll see. So this is what it did. You add an option, use random colors, which does this. What do you think? Would you use this? Would you use this? There has to be some discussion about this and at the end it was preferred to actually still make this available for everyone so you can use this right now but on the KD Store instead of being part of KD Plasma. And that's very nice thing I think because even if something gets rejected, we could say even from the community, you can still propose it as part of the KD Store and anybody can still use it. It's just not part of the default install but it's still there to be used. This one then. This one is literally a one line change that is pretty important. So if we are searching for something in system settings like the name of a category, then we might tie for, I don't know, this is GNOME search as an example and I could search for audio like this. And if I search this, I expect the audio category in system settings to open up if I'm in KD. Now, what I typed is audio lowercase but maybe this action is actually audio with the A capitalized. So what this does is simply saying if the keyword starts, the keyword being actually the keyword in the system settings file. So as an example, audio could be a keyword of the sound KCM. If it starts with the query, then I mean, we are checking if it starts with the query but do this in a case insensitive way which is pretty important. And just like that, it makes results of KD runner when searching for system setting sections more reliable. Last one, this one is the before, this one is the after, let's compare them, this, this. So you can see that instead of having power safe balance performance, now there are just two icons on the left on the right and power profiling performance on the top. So we basically killed balanced and we added icons. So why balance was killed? Because of German, I mean, some languages like German are very long and they don't actually fit the space that it's given them by the UI and so they get elided. So it was discussed how to avoid this and eventually we were like, okay, let's just get rid of the middle one. Now there's enough space but to make this more clear, let's actually add the icons. Let's give a look on how this is done, changes. So we've got a row with first element, a label which is power profile, is it? Second element, another label with a text being the active profile data label which probably is the profile that you're using. So performance is going to be written performance, balance is going to be balance, power safe is going to be power safe. In here, we actually add the repeater of, where is it, labels to actually write all of the profile data names to have all of them. Now it was removed because there was not enough space. Then we add an SVG which is icons battery SVG which is not actually an SVG element in the UI. It's just a reference to be used later by the SVG item. The SVG items takes the SVG that we defined here. We ask for the element called profile power safe and then we say, okay, it should have this size. Similarly, here we've got another element from the same SVG and this is why the SVG declaration is separate. This time we want the element profile performance with this size and between them just an empty item that fills with to make sure that this is left aligned and this is right aligned and that's it really. This adds a couple of ideas but it's mostly unrelated I think. So just like that some pretty nice feature of KDPLasmo were implemented and sure we are not talking about incredible changes which will change everybody's life. Like I mean, one to one just saw incredible changes. This one maybe aren't but when you're using KDPLasmo day to day well being able to search for system settings in key runner or kickoff even is pretty important just like it is to being able to see what profile you're selecting just like it is super important to be able to set a random color to your wallpaper every second I guess for somebody. So thanks for following and see you tomorrow with another video.