▲ 181 points
back
72 comments
Anyone know how we can provide features and sponsor them for KDE 6.
I've wanted to pin virtual desktops to a specific monitor (same as i3) and be able to independently switch virtual desktops on each monitor.
Its a widely requested feature which hasn't landed, I was hoping to get this on their radar and if necessary pay for this feature. Its something that's been bothering me since KDE 3 days.
I suppose you could mail one of the KDE mailing lists[0] to ask about this. Probably you want either kde or kde-devel.
The one thing holding me back from switching to KDE in full. The hacks and Kwin scripts just simply aren’t enough.
If you find out more on this (solutions or ticket to sponsor) please update!
Have you tried to directly run i3 instead of KWin? https://github.com/avivace/dotfiles
Thanks for the link!
I had found a few pieces of the repo's Readme but this looks solid, I'll have to give it a try.
If you're on X, there's no reason why you shouldn't just use i3 on the top of Plasma. https://github.com/avivace/dotfiles
Take a look at TDE/Trinity.
I do not know if it does as you wish, but it is a fork of kde2, with enhancements, and they are actually open to actual, usable, needed change.
Are you implying that the KDE devs are not "open to actual, usable, needed change"? That seems disingenuous given the multitude of actual, useable, needed changes they make.
Trinity exists due to unusable, unneeded change that is kde4 and beyond.
So no, they are not open to that path.
Right, I misspoke.
Hats off to the KDE team for a really great release cycle. I understand that there were some licensing issues with Qt in the back half, but Plasma 5.27 really pushed the Wayland session into excellence. It's unclear what Plasma 6 is going to look like, but they've got a damn fine launchpad with the current KWin Wayland session.
I thought that Plasma 6 will look exactly like Plasma 5, the only change being the Qt version they depend on.
For the short term. Longer term they will make improving things and following whatever the next fad is - just like everyone else.
Probably, I don't anticipate many changes from what they've got right now.
I personally hope that one of the first new UI changes to land in Plasma 6 is support for rounded window corners in all corners, not just the titlebar ;)
You only seem half-serious, so I suspect there's something I've missed about KDE corner history.
Anyway, 'picom' can at least grind down those edges (or smooth out, depending on your point of view)
#################################
# Corners #
#################################
# Sets the radius of rounded window corners. When > 0, the compositor will
# round the corners of windows. Does not interact well with
# `transparent-clipping`.
corner-radius = 5
# Exclude conditions for rounded corners.
rounded-corners-exclude = [
"window_type = 'desktop'",
"window_type = 'dock'",
]There's an infamous very, very long dev discussion thread on the quo vadis of bottom corner trimming (with working patches) :-)
I am mostly serious. I mean, it's not a huge deal, but it would look awesome :)
I guess maybe I could look into picom. There was also a third party kwin plugin that could do the same thing IIRC.
5.27 is the first KDE release in a while that has actually broken things for me. Fedora recently updated to it and the breeze theme broke, causing me constant crashes and glitchy window decorations.
Whenever I hear about completely broken KDE installs, it's Fedora in 90% of cases.
Yeah. In my case, the Discover app didn't fully update all of the packages like it was supposed to. Easy enough of a fix, though I doubt an average PC user would have been able to figure that out.
Is this the Qt version that drops the custom metaprogramming stuff for QObject and friends and adopts modern C++ in its place? If so, it's a very cool development! :)
Nope, Qt 6 still uses moc. I don't think modern C++ metaprogramming is quite capable of entirely replacing moc. The closest thing I'm aware of is [0], but it requires additional macros compared to what moc requires, and compilation speed can suffer. Chances are moc won't be dropped until full reflection lands, if ever, and even then if compilation speed is too bad I wouldn't be entirely surprised if moc remains.
yep, a big part of moc is about generating reflection info and current C++ metaprogramming very simply does not cover reflection and even less custom code generation (think generating a function called "auto foo_info()" from a function "void foo()" automatically - right now the only way to do this if one does not want to use macros is through an external code generator, e.g. in CMake or whatever).
Apart from just not having all the widgets, why do you think CopperSpice falls short? Getting rid of the moc was pretty much the first thing they accomplished.
It is possible to get rid of moc by manually writing out the equivalent code (using macros or not) or gutting out features that require it. Qt uses it to do things that would otherwise not be possible, like expose QObjects to scripting languages. That requires reflection that modern C++ doesn't support and thus needs either redundancy of some kind (to generate the necessary metadata to do 'reflection') or code generation (to generate the necessary metadata to do 'reflection').
MOC was never simply superfluous.
Never quite sure why people are so fixated on moc. It's by no means the most annoying thing about Qt and it works well in practice. The signals/slots mechanism is one of the best things about Qt.
So like a decade ago I hated using MOC because it would mess up auto-formatters and source code parsing in all editors, but since clangd/clang-format and its LSP friends, working in Qt and having stuff like the autoformatter work perfectly has since alleviated any problems I have with using the MOC.
Now they're just equally as annoying as any other macros are, which is to say, a lot less annoying than it used to be.
I think it would be interesting from a C++ perspective. That was my point. Qt is awesome as is.
Is this the Qt version that enables custom date formatting? So that one might be able to configure, e.g. YYYY-MM-DD date format, week starts on Sunday, H:i:s time 24 hour time with leading 0, and with the period (dot) decimal separator?
Does Autodesk still only use the LGPL licensed Qt to avoid paying a single cent to The Qt Company?
I think it's weird that big megacorps don't actively support the very foundation their software is built upon.
Someone has to sign the cheque. That number is going to come off of their results. The tragedy of the commons happens within companies as well.
I celebrate these news with a bit of unease. I've heard a lot of criticism regarding Qt 6 licensing policy. And personally I'd rather prefer more stability.
The licensing policy in Qt 6 isn't really changed vs. 5 -- the change that upset the community was the commercial-only LTS releases, which started with 5.15.
KDE has been maintaining Qt 5.15 by itself with the "KDE Qt Patch Collection" since then, as the 5.15.y bugfix releases are commercial-only for a year before they get released as open source.
In Qt 6 the situation is theoretically better as you get a new 6.x feature release faster than that one-year wait period, whereas 5.15 was the end of the line for Qt 5. The commercial-only also only happens after the first two bugfix releases, so there should be no significant waiting periods without releases. If the general quality of Qt releases is sufficiently high, the Patch Collection effort may no longer be needed.
That said, The Qt Company remains a topic of concern, publishing (also on LinkedIn by employees, with lame/thin "does not necessarily represent my employer's opinion" disclaimers) lots of "why open source software is scary" content lately, apparently unaware that the only reason anyone cares about their product is its open source pedigree and credibility: https://www.qt.io/blog/is-open-source-really-free
This is probably a reaction to competition by the BSD-licensed Flutter which has seen a lot of interest from their traditional commercial audience. Doubling down on "we're less open source" as a differentiator vs. _Google_ of all companies is quite a mind-bender. Also considering licensing/open source is why Flutter is getting that attention in the first place, and that Qt could tell a fantastic story here if it wanted to.
> That said, The Qt Company remains a topic of concern, publishing (also on LinkedIn by employees, with lame/thin "does not necessarily represent my employer's opinion" disclaimers) lots of "why open source software is scary" content lately, apparently unaware that the only reason anyone cares about their product is its open source pedigree and credibility: https://www.qt.io/blog/is-open-source-really-free
I don't think that article is really pushing for Qt to go closed source; rather, they're just trying to sell commercial subscriptions in order to make money (after all, the Qt Company has to stay alive somehow). And Schnieder makes it clear that building your stuff opensource is not a bad idea in many situations; he's just promoting Qt's commercial subscriptions (which IMO really are probably nice for corporations who want priority support and who don't want to deal with licensing issues).
The big thing that put me off Qt 6, even though I’ve been a fan of Qt in the past, is that I cannot download the official release, even if the LGPL version, without registering an account, while before you only needed that if you wanted a commercial license or to use their other services.
Don't be. There is legally binding contract that prevents Qt Company from unilaterally changing the licensing deal (until KDE stops using Qt).
Qt is a great example of how you can force commercial highly profitable company to develop open source against their will even after it's sold multiple times. Trolltech and KDE jointly formed the foundation to make sure that Qt core stays open source.
Licensing agreement has not changed. Qt Company just stopped doing anything not required by the agreement between The KDE Free Qt Foundation and The Qt Company. https://kde.org/community/whatiskde/Software_License_Agreeme...
> And personally I'd rather prefer more stability.
Time flies. Qt 6 has been around for more than two years already! And from what I understand, the change from Qt5 to Qt6 is a much smaller transition than the one from 4 to 5.
Hmm maybe "smaller" but there was more stuff that just didn't exist (or work properly) for a year and a half in the 5->6 transition as there was in the 4->5 transition. I went through both transitions and this one was more of a pain.
Nice!
I was waiting for this to happen so $HOME/.kde would be finally removed for good.
I wonder how long will it take for all major KDE apps to move to Qt 6? Or is this trivial, as they are using KDE libraries?
KDE's apps Plasma use the same set of libraries (KDE Frameworks), and Plasma only made this move after the Qt 6 port of the libraries achieved a certain level of maturity. This in turn has also enabled many app ports already. In a way, the Plasma bits are a somewhat later step in this campaign as some of the hardest to port pieces that need the most supporting infrastructure.
You can check up on overall KDE-wide progress here: https://iskdeusingqt6.org/
Will that finally give me ISO dates in all my kde programs (mainly dolphin)?
Hopefully KDE 6 has a modern theme, Plasma is very 2015.
2015 it's modern enough. I use an IceWM style mimicking Motif and a Solaris 8 theme close to OpenLook/Motif, so anything which came later than 2008 looks the same to me.
Leave KDE alone!
Seriously, it's the last DE that seems to be doing something else but to make everything ever flatter and more whitespacier. I like the slight retro touch to Breeze, makes everthing more visible.
They need to update to modern design, a minimalist Apple GUI aimed at tablets.
Lol, if you think Gnome is an apple copy, you haven't seen any of the new Chinese DEs.
Also from experience, Gnome absolutely destroyes MacOS in usability, macOS is really crappy.