For many years now KDE has focused on polish, bug fixing and "nice-to-have" improvements rather than major redesigns, and it paid off.
For many years now KDE has focused on polish, bug fixing and "nice-to-have" improvements rather than major redesigns, and it paid off.
VDG tackled (and tackles) not only design for the desktop itself, but also for KDE applications that had never seen a designer's touch before.
I've been long a KDE user, even through the 4.0 troubles, but also the first to admit that it used to look clunky. Looking at old screenshots is a quick reminder of how far this initiative has taken it.
I love open source and have been running Linux since 1999, but my experience of contributing to both KDE and GNOME is your PRs never go anywhere unless you're part of the inner cabal of maintainers, otherwise any small bugfix or feature goes into bikeshedding mode, and it's the reason I don't contribute any more.
That said, I run KDE now after two decades of GNOME. It's pretty good and has been looking good for a while now.
What's up with the massive amount of chrome used for nothing except new tab/copy/paste buttons? Is it really necessary to take up what could be used for 2+ extra lines of terminal output for a labeled Copy button? Compare it to gnome console, or any other terminal really, and you will get far more terminal output for the size of the window, as it should be.
And it's not just Konsole. So many KDE apps have this same problem. Giant labeled buttons taking up space from the actual content, for things you will never use or have well established keyboard shortcuts already.
https://mero.ng/i/lWMWazUP.png
The screenshot on the website has all sorts of optional bits enabled, and I would readily agree is not a good showcase.
The reason all those optional bits exist is because you'd be surprised who ends up using a terminal emulator in a general purpose desktop GUI used in many large IT deployments. E.g. a lot of folks who are used to PuTTy on Windows and want a little GUI for SSH connections, and for them this is the game changer.
The "try to show all the goods in your screenshot" mindset is really not a good one though, agree :)
- Change encoding? I have never changed the encoding of my terminal, not once since first using a computer, circa 1982. UTF8-FTW.
- Adjust scrollback, on the context menu?
- If you hide the toolbar/menu I believe it adds the main menu to the context menu. And that is where the majority of the hundred options live. And at the end, where a Properties or Preferences entry should live.
- Last but not least, no "New Tab" entry, which is the thing I use it for 90% of the time.
All of which are useful
> Change encoding? I have never changed the encoding of my terminal, not once since first using a computer, circa 1982.
Then you've never worked with Japanese. Which is fine, but a significant proportion of the world needs to.
> UTF8-FTW
Not for Japanese, sadly.
Also neglected the point elsewhere that obscure options are fine in control panels, auxiliary and submenus.