 Hello and welcome to yet another episode of a Reddit thread in arrow slash kitty has gotten something like 200 responses. So I actually wanted to go through them and try to provide a somewhat useful commentary that was a long title. So, you know, these kind of things sometimes happen, somebody like puts out a very general question in arrow slash kitty, and then there's like 300 answers. And usually they're interesting. Of course, it doesn't mean that doesn't mean that all of them should like immediately be implemented in kitty or anything. It's food for discussion, nonetheless, it is food for discussions. So today's question is what features is kitty missing according to you. I have no interest in interest, sorry, in, you know, providing my answer. My job here is mostly to do this boomer thing of going through the comments and, you know, try to provide commentary as a set. So let's start off with import, export in a single option for all themes and personal life settings. That is actually something that I hear a lot and I can understand why. So there kind of was something like this in terms of plasma config saver, which is an applet that you can download and use. I have done a video about it and it allows you to save your entire configuration, sorry, of kitty plasma to a single file and then load it and it works. I had tried it. However, for the very latest version of kitty plasma, I've been told that it broke in an update. I'm not sure I'm not following the project actively. However, do know that there is that project if you and if you're interested in something like that, there is this kind of option. Keep in mind, however, that being able to actually important export in a single option for all themes and personal life settings, it's kind of impossible to do in a safe and reliable way, especially because a lot of kitty settings rely on having something installed. As an example, if I have set a custom plasma theme, then I have that plasma theme installed and not necessarily have I installed it through the kitty store. Maybe I just downloaded a folder, something like that, which means that if I try to do that, like if I try to export my settings and then import them back on a different computer, what that different computer won't have any clue where to get this plasma theme from. And I guess you could package it inside of a zip directly inside of the settings, but that would be a mess because it would result in a file that's super big. Also, sometimes you have stuff like Kevan to or lightly, which are third party application themes, which are based on like, which are built with the C++ and you can just, you cannot just pack them in a zip. You actually have to install it whenever you want to use them. And that is not something that kitty plasma can do at all because it depends on the destroy depends on whether they are packaged. If they aren't, then you have to build it yourself and kitty plasma can like start building stuff on your computer. So that is completely unfeasible. So it is something extremely complex because kitty plasma customization is so powerful and not everything you can just put into a folder and it's going to work. How would you actually export all of kitty plasma settings? So what plasma config saver does, which is interesting is that it saves just the config files, which means that if you try to use the same config files into a computer that does not have the same plasma theme or does not have lightly or Kevan to me, if you're using them, it's just not going to work because you don't have them installed and nobody except for you can install it for you. So you have to do it yourself. So I mean, I get a point, there is something like that, but to implement it safely and robustly is borderline impossible for us. I think centralized config directory. This is very interesting. There has actually been a discussion after reading this comment in the off topic room, I think. And the thing is to have a centralized config directory for all kitty files is absurd. It's an absurd request. Where's that? So KDE is not a desktop environment. Let me repeat that. KDE is not a desktop environment. KDE is a community of people that has a lot of project going from a desktop environment, which is called plasma and not KDE, but also lots of applications, as an example, but also frameworks, all kind of stuff. So where's the issue? Well, it makes no sense whatsoever to try to take all of this at desktop environment, lots of applications, frameworks and put all of the config files, all these things together in a single directory. That would mean that your plasma file config files and pre-tag config files and dolphin config files or discover config files and frameworks file, all of these things which are very different are all stored together. That makes no sense. Just like it makes no sense to have a like, if somebody asked for Firefox to save their own config data for Firefox in the same place where plasma saves its own Firefox is Firefox, Plasma is Plasma, different things which with different, you know, scopes, it doesn't make sense to try to make them the same when they saves the config files. Same goes for all of the stuff that KDE does. Now you could make a point that some KDE products like Plasma, as an example, do not have their config files like clean enough. Like, I think Plasma config files are split in a couple of directories, I think, if I recall correctly, which is a fair point. Of course, the reason behind that is technical issues, which I won't get into, but just keep in mind that having a KDE config directory doesn't actually make sense at all. You could have like a centralized Plasma config directory. Another thing could argue for that. Currently, we don't have that to do technical reasons. Touchpad pinch to zoom. This is funny because the first time I read this, I immediately tried to do pinch to zoom, like to see what happened. And this happened. So pinch to zoom actually works in Firefox and that's pretty much it. Not very exciting, not very KDE. It is a fair request. It is very much a cool to have. Currently, I am personally not aware of any work in that projection. However, this is very, this is stuff that is directly linked to QT, the framework that actually draws things on the screen for us. And I don't follow that, that so I am not sure. Per virtual desktop wallpaper. You know, it's like, okay, first of all, that is activist, like, activities are meant to address that. Just like the second comment is, and widgets, that is the point of activities. You have different activities and each activity can have its own wallpaper and its own widgets. That is the whole point. Virtual desktops is something which is much lighter as a concept. It's, you know, just virtual desktops. That is multiple desktops for the same thing happened. You start asking for more customization on virtual desktops on top of the one that we already have, which does the same thing for activities. You're asking virtual desktops to kind of become activities, which is something that could be discussed. The issue is the complexity that this would bring. We always have to think that everything we do will bring some complexity with us. And I think that's really what killed off activities, like vertical concept with its own flows, if necessary, but super complex. And even implementation for me, often it has too many bugs. So I just use virtual desktops at this desktops at this point. I think that if we try now to add a lot of stuff to virtual desktops, it's going to become a mess, like to maintain the bug. I'm really not a big fan of it, but that is I'm not a Kiwin maintainer. So take that, of course, with a green of sale to everything I say, customize touchpad gestures. Yeah, yeah, yeah. The answer, which is to use Libinput gesture as far as I know, doesn't address that at all. Like I think Libinput gestures implements its own gestures that are not really integrated in KD Kiwin. So I would suggest against it. I mean, if it works for you, it works for you, but we should have some way to customize the touchpad gestures. I fully agree. And I think there's nobody that is against this. It's just a matter of actually implementing this. Again, as far as I'm aware, there is nobody actually working on this actively. But for this in particular, I might be wrong because I saw some messages regarding this, but it's really just a matter of finding somebody to do this. Nobody's against it. KD connect. This is another good example. I think would be nice to have a possibility to sync the directories and not only send files. Okay, again, this is very much a matter of complexity to do something like that is very tough, like genuinely tough, which means people need like more than one people need to develop it and then maintain it through time. And it's going to be complex. It's going to take work time, which by itself is like not an issue. If not, that we have syncing syncing does exactly that. Like it's the whole reason syncing exists. If I've talked about syncing before, if you don't know it, try it out very cool. And it does that it does sync, syncing for directories between phones and other devices on the same network. So it doesn't make sense at all for KD connect people to try to reimplement exactly what the syncing already does. But the result would probably be worse because syncing has been developed for a lot of time. So another possibility would be to try to implement syncing inside of KD connect. But at this point, just use syncing because there is a tool to do that and try to take trying to take that tool and put it forcefully into another tool that does something different, especially if this use case is very complex, like syncing directories, syncing directories is not simple. It's going to create a mess. I don't know. So my suggestion here would be using thing notifications on the lock screen as far as I know are being developed. I think I'm not exactly sure by how, how's the work going? I haven't followed that. I just know that somebody's somewhere is kind of working on it. So should come eventually, which is great news. And I fully agree that we need them. We totally need them. Rock solid stability is something very interesting that is completely different from what has been asked so far. And to be honest, I agree. Like I would like KDPLasment channel to be solid. Keep in mind, however, that rock solid stability is often mutually exclusive with having lots of features just like they were asked in the post previously. Like if you want to have rock solid stability, then you totally don't want to have her widgets wallpaper, like being able to customize the wallpaper depending on the virtual desktops. You don't want to have widgets different widgets, depending on the virtual desktops, all of these kind of things create complexity, which decreases stability necessarily. Could with time, like make sure that they work nicely. But that is not the path towards rock solid stability, especially in considering that we do already have a super high degree of flexibility, which is already causing us some headaches. You might not realize it, but to make a stupid example, you know how we have plasma themes, which allow you to customize plasma in any way, like the look of plasma. That sounds very cool up until I have to implement something new, like a better look for the switch, the switch component, you know, the one that goes left and right. I have to revamp how it looks to make it look decent. It's going to be a mess. And it would be super easy if we didn't have things at all, but we do have, which means it's going to be a mess because of a lot of reasons. And on top of just that mess, just to implement that switch for the default theme, there's also a lot of the question of will third party plasma themes be able to customize this component as they want? Can we offer more customizability? These kind of things, it creates a lot of complexity and headaches necessarily, but it's why we do KD, right? So I agree. And keep in mind that stability and lots of new features kind of mutually exclusive up to a certain extent. Regarding out of the box short directories, NFS and Samba, I don't know about NFS, but I'm sure Samba is supported out of the box with Dolphin. If you do have the correct package, as the comment is replying to, it wasn't super like polished up until recently. I think that in the last year or so, there has been quite some merger quest to polish it up, which was nice. So it should work. I have no clue whatsoever about NFS, to be honest, separate virtual desktop per physical monitor is another of those complex things to address. It's not that necessarily we shouldn't have that, but not super easy to address it. But I think it's maybe more easy to, I don't know, because we already rely somewhat to the fact that this doesn't happen. I don't know about this one. I should like talk to the Kiwin developers. So I don't know. Better tiling, but there is something on the way. So there is the patch from Marco, which I showed case on this channel on the way indeed. Not just that though, you can have B smooth and other Kiwin scripts to do that. And I really want to emphasize that the fact that these scripts are third party doesn't mean at all that they are any worse compared to if they were built in. That is a very important point to me. So I see people asking like, I'd like something baked in, are you sure? Are you sure of it? Because sometimes the stuff that you do baked in is significantly worse compared to what exists the third party because KDPL is so customizable that what for other projects is usually baked in for KDPL is third party. Like usually other projects do have this plugin system. I'm not talking about like, no, but other projects much different from how KDPL works have a plugin system that is not exposed to the user, but it is for like internal development similarly to Kiwin effects. And in KDPL, all of this is exposed so a developer can add an effect or a script and the user perceives that as third party even though it's not as far as quality goes. You know, it's as good as if it was baked in. It's basically baked in desktop cube. I don't know. Maybe it will come back. I honestly don't know. Like there was a developer that has ported back to QML the flip switch and the cover switch. And they were interested in porting the desktop cube as well, I think. However, there was this thing that when they ported the flip cover flip switch and cover switch effects, there has been a negative reaction because they hadn't brought them back exactly as they looked before. They had some like blurring and stuff. They looked prettier. And of course, people were annoyed by how it looked slightly different. And they opened back report and then they complained a lot. And that is exactly not how you try to convince that developer to continue working on this kind of stuff. If you start complaining about the work they've done and opening back reports, it's difficult for them to find the motivation to go on and also bring back the desktop cube, especially because you know, they are probably doing it on their free time, just like I am. So be kind if you want this kind of things. And it's not like it was considered a silly trivial thing and let go. It's that a the number of people that used it are a minority, a small fraction of KDPasma users. And that is a fact you can go around it. That doesn't necessarily mean by itself that we should get rid of it. We don't get rid of things just because they're used by a fraction of people using KDPasma, obviously. However, it was also creating issues. It was legacy, difficult to understand and maintain C++ code base. And at the certain point, the cost of trying to maintain alive this effects was greater than the benefit that it gave us. And at that point, it was let go to get the desktop cube as well back, sorry, then you would have to have it as a QML effect, which is much easier to maintain and, you know, with the code revamped. And so far, as far as I know, nobody has done that. I think it was kind of in progress, at least at a certain point, but I didn't follow their discussion. Fancy zones are coming. Dynamically created virtual desktops. I'm pretty sure there's a KWin script that does that. So that we already have that. So that's nice. Automatic automatic back message and drink ice dispenser. I fully agree. This is like the top priority feature that I would look for right now, especially with this terrible cheer that I have, the ability to rearrange the position of three icons is again, a very good example of complexity and stability. Like nobody, literally nobody is against the idea of being able to reorder three icons. However, when you actually start thinking about the fact that you have to implement it code wise, and you look at the code that is in the tree, well, you start being like, what about no, I think that the proposal was actually closed for in the past by some developers who said, okay, no, this would bring so much code complexity that it's not worth it. Then I think it was opened again. So right now there is an open bug report for this one day. I would like to try to implement that. But if I see that the code is a mess, the code is a mess and I won't touch it. It's as simple as that stackable or multi row panels, you want to kill me? Whoa, that is something so complex. Is it multi row? It's not necessarily complex now that I think about it. Why are you giving me these ideas? Come on. It's like, in theory, I guess it's possible to have multi row. However, being able to have a UI for it and then be able to go to edit mode and then reorganize the widgets between the two rows. Oh, I really don't want to deal with that, honestly. I will give a shot to see how it works. Maybe it's like super easy and I just have to enable a couple of things. It's not a terrible idea. But again, the panel is a fundamental component of Kiri Plasma. It has to be rock stable. If I see that it brings any complexity that shouldn't be the panel in, no way I'm implementing that. The panel is already too complex for what it's supposed to do. So no, no, no, no, no. Search in up menus exist. You do get it, I think in the help menu of the application. If you're in Wayland, I think that is a thing or was a thing at some point, I don't know. But you do also get the K command bar component, which is super cool, which is control alt I, which does that you can search through the upper menu by pressing control alt I in like a lot of kd apps, not all of them, but a lot like Kate use the command bar in Kate because it's so cool alt control I. So it has been half an hour since I started talking. I think that's way more enough. But if you want some comment about something specific, you can always ask me if I don't answer to your comment. Sorry. Sometimes it's busy. I saw comments which are like, why did you do reply to my previous comment? Sometimes I'm busy. Sorry. I tried my best. But thanks everybody for following along. And what else? See you tomorrow, I guess, with yet another video. Bye. I forgot to stop recording.