4 ms·

>There's always something that is not right in the UI foundation What is fundamentally broken with their UI that a competent person can't change?

agumonkey 7y ago
the whole
- simion314 7y ago
  Thank you for your thoughtful and intelligent response, I think there is a DE that is more for your level, is safe it has all big and rounded widgets and most of the features were removed to make place to even more white space to look professional but be basic.
  - agumonkey 7y ago
    thanks, it's always easier when questions are that thoughtful
ubercow13 7y ago
Often with newer UI frameworks like that used by plasma, basic interactions with familiar widgets just don't work as expected. It's the same argument levied against any non-native app whenever this comes up, whether it's QML or Electron or whatever. As a concrete example, the KDE application menu will close whenever you move the cursor off of it onto another window, unlike any menu in any other desktop UI widget toolkit [1]. So from some users' perspective, things like the move to plasma can seem like little more than a series of UI regressions. The basics just don't work so well any more, and the only upside is maybe slightly prettier graphics. It can be disheartening. Here is an application menu from KDE 1 in 1999 which I am sure worked just fine [2]. [1] https://www.reddit.com/r/kde/comments/9a41si/possible_bug_application_menu_closes_when/ https://www.reddit.com/r/kde/comments/9a41si/possible_bug_ap... [2] https://en.wikipedia.org/wiki/K_Desktop_Environment_1#/media/File:KDE_1.1.jpg https://en.wikipedia.org/wiki/K_Desktop_Environment_1#/media...
- agumonkey 7y ago
  this is part of it, and a too complicated layout grid it seems.
- simion314 7y ago
  It seems to be a bug but for me personally Plasma is not the reason I use KDE, I love KWin and krunner and all the other applications. KWin the window manager is very configurable so I can do a lot of things with it, krunner I launch my apps with it without using the mouse, the file manager is configurable and good for my use cases, the text editor is also very decent for small and quick edits. On top of that GTK2 and GTK3 apps are integrated as much as possible. If other DE matches you needs better and if it does it by default then I am happy for you I am not trying to sell you anything.
johnchristopher 7y ago
The fact that today I accidentally deleted $XDG_DATA_HOME instead of \$XDG_DATA_HOME (somehow `# vim` keep re-creating that directory) in my $HOME folder and now I can't seem to bind META+T to Konsole and META+E to Dolphin. Any other applications, I can bind. Any other shortcuts I can. But Meta+T/E to Konsole/Dolphin, I can't. Fortunately KDE doesn't seem to store much in ~/.local/share (which is where $XDG_DATA_HOME points to). edit: ah, a reboot later and it works as usual... go figure (not saying it's KDE's fault, it maybe be an .xprofile or some .voodoo mismatch). And the fact that some options in the default configuration panel can actually only be used when you chown certain files to root (the login manager background for instance). I love KDE though, the UI is way cleaner than it was before, it's fast, the whole desktop feels visually coherent, but it still feels like climbing a tree with a gazillion branches when configuring it through the configuration UI. (and someday the automatic sound output switching will work, but not today)
- simion314 7y ago
  I am not excusing KDE here, I can't be sure but there is a chance that is a packaging/distro issue. My question was for OP to present the fundamental UI issue, I am sure there are hundreds or touand of bugs in the KDE bug tracker but I am not aware of a fundamental issue unlike the other popular DE that has a major architectural issue .

agumonkey 7y ago

the whole

simion314 7y ago
Thank you for your thoughtful and intelligent response, I think there is a DE that is more for your level, is safe it has all big and rounded widgets and most of the features were removed to make place to even more white space to look professional but be basic.
- agumonkey 7y ago
  thanks, it's always easier when questions are that thoughtful

ubercow13 7y ago

Often with newer UI frameworks like that used by plasma, basic interactions with familiar widgets just don't work as expected. It's the same argument levied against any non-native app whenever this comes up, whether it's QML or Electron or whatever. As a concrete example, the KDE application menu will close whenever you move the cursor off of it onto another window, unlike any menu in any other desktop UI widget toolkit [1]. So from some users' perspective, things like the move to plasma can seem like little more than a series of UI regressions. The basics just don't work so well any more, and the only upside is maybe slightly prettier graphics. It can be disheartening. Here is an application menu from KDE 1 in 1999 which I am sure worked just fine [2]. [1] https://www.reddit.com/r/kde/comments/9a41si/possible_bug_application_menu_closes_when/ https://www.reddit.com/r/kde/comments/9a41si/possible_bug_ap... [2] https://en.wikipedia.org/wiki/K_Desktop_Environment_1#/media/File:KDE_1.1.jpg https://en.wikipedia.org/wiki/K_Desktop_Environment_1#/media...

agumonkey 7y ago
this is part of it, and a too complicated layout grid it seems.
simion314 7y ago
It seems to be a bug but for me personally Plasma is not the reason I use KDE, I love KWin and krunner and all the other applications. KWin the window manager is very configurable so I can do a lot of things with it, krunner I launch my apps with it without using the mouse, the file manager is configurable and good for my use cases, the text editor is also very decent for small and quick edits. On top of that GTK2 and GTK3 apps are integrated as much as possible. If other DE matches you needs better and if it does it by default then I am happy for you I am not trying to sell you anything.

johnchristopher 7y ago

The fact that today I accidentally deleted $XDG_DATA_HOME instead of \$XDG_DATA_HOME (somehow `# vim` keep re-creating that directory) in my $HOME folder and now I can't seem to bind META+T to Konsole and META+E to Dolphin. Any other applications, I can bind. Any other shortcuts I can. But Meta+T/E to Konsole/Dolphin, I can't. Fortunately KDE doesn't seem to store much in ~/.local/share (which is where $XDG_DATA_HOME points to). edit: ah, a reboot later and it works as usual... go figure (not saying it's KDE's fault, it maybe be an .xprofile or some .voodoo mismatch). And the fact that some options in the default configuration panel can actually only be used when you chown certain files to root (the login manager background for instance). I love KDE though, the UI is way cleaner than it was before, it's fast, the whole desktop feels visually coherent, but it still feels like climbing a tree with a gazillion branches when configuring it through the configuration UI. (and someday the automatic sound output switching will work, but not today)

simion314 7y ago
I am not excusing KDE here, I can't be sure but there is a chance that is a packaging/distro issue. My question was for OP to present the fundamental UI issue, I am sure there are hundreds or touand of bugs in the KDE bug tracker but I am not aware of a fundamental issue unlike the other popular DE that has a major architectural issue .