https://bugs.kde.org/show_bug.cgi?id=443410
--- Comment #6 from Aragorn <thoron...@telenet.be> --- (In reply to Vlad Zahorodnii from comment #3) > This was discussed back in May. See > https://mail.kde.org/pipermail/kwin/2021-May/005222.html for the reason why > the effect was dropped. > > I'm afraid that we can't bring the effect back because rendering > abstractions have changed quite a bit. One would need to rewrite the effect > from scratch. As discussed in the mailing list thread, we would like to have > the effect reimplemented in qml (like the overview effect), but we don't > have man power resources to do so. It will be great if the community helps > with the port of the effect to qml. Forgive me for sounding hostile, and I fully appreciate that the effect(s) would need to be rewritten in order to ensure compatibility with the evolution of the Plasma desktop, but from the email exchange you've linked to here-above, it appears to rather be a matter of not having any motivation to do so instead of a matter of not having the manpower or the resources, as well as a matter of not being in touch with your user base. You are all in control of how Plasma works and how it evolves. Therefore, you are also in control of which aspects of the software you wish to advance to the next level first. If the new "scene" ─ as you guys call it ─ requires the rewriting of those effects, then perhaps you are pushing out this new "scene" prematurely at the cost of breaking existing features, and ─ forgive me for saying this ─ you guys unfortunately have a history of doing that. Plasma 4 springs to mind, as well as that it took you guys until 5.10 before the global menu ─ a feature that had already more or less been present (even if only for Qt applications only at the time) in KDE 1.x, 2.x and 3.x ─ was reintroduced, in spite of the very popular demand throughout the entire life cycle of Plasma 4 and up until 5.10. There's an old saying that goes "If it ain't broke, don't fix it", just as there is another saying that goes "Whatever you're going to do, if you're going to do it, then you should do it well." If you break something, then you're also taking the responsibility upon you to fix it again. Don't hide behind the excuse of not having the resources and/or the manpower. Again, I've read the email exchange that you linked to, and it's not a matter of "we don't have the resources", but of "let's just drop it, because hardly anybody's using it anyway." It's not the resources that are the problem; it's the attitude. -- You are receiving this mail because: You are watching all bug changes.
