https://bugs.kde.org/show_bug.cgi?id=377162
--- Comment #97 from Neal Gompa <[email protected]> --- (In reply to Daniel C. Würl from comment #96) > (In reply to Nate Graham from comment #89) > > Anyone who becomes one of those people actually doing the work by submitting > > code to implement window shading on Wayland in a way that doesn't cause > > architectural problems will be taken seriously. Clearly there's some demand > > for it. > > > > But until that happens, this feature is gone on Wayland. If this frustrates > > you, the solution is what I mentioned: help build a maintainable, > > Wayland-compatible implementation of the feature. > > (In reply to David Edmundson from comment #60) > > With the prevalence of CSDs we cannot reliably do shading for enough apps to > > provide a reliable experience. I would reject all patches attempting to add > > it. > > Maybe I'm misunderstanding something here: > > - Wayland can't do window shading, despite it being implement on wayland in > labwc > - The existence of Client Side Decorations and the feature set of Mutter, > which is intentionally limited to Gnome's own CSD, rules out implementing > window shading in kwin, despite window shading being one of the very reasons > KDE didn't go the CSD route back in the days according to the former kwin > maintainer > (https://blog.martin-graesslin.com/blog/2010/05/open-letter-the-issues-with- > client-side-window-decorations/). > - Any patches will be rejected > - But unless patches are submitted, nothing will be done > > This doesn't exactly induce people to contribute, it feels a bit dismissive, > with a taste of catch 22. > > > (In reply to Nate Graham from comment #91) > > > This is a concrete example of why "noise in the bug report makes the change > > less likely to happen." I imagine most developers have unsubscribed, muted, > > or ignored notifications about this issue because of all the > > non-technically-useful comments. > > Do I understand correctly that the more users push for a feature, the less > likely it is to be implemented...? > Seems counterproductive somehow. > > I'd also like to clarify that this noise mostly sprung in reaction to > dismissive, avoidant and plainly wrong statements made by some devs here. Unless you and everyone else can both convince the contributors the feature is a good idea *and* provide some funding to allow the volunteers to deal with the opportunity cost of working on this fairly complex feature, I don't think you'll find any alignment of incentives to get it implemented unless you are a software developer and willing to dig into the code yourself to get it implemented. There is nothing about Wayland that fundamentally prevents the *possibility* of the feature, only the *universality* of it. For example, if the application doesn't allow server side decorations at all, it's going to be really awkward to use -- You are receiving this mail because: You are watching all bug changes.
