Back to the subject: good progress coming from Wayland and Gnome. Day after day Canonical's decision to start Mir seems more and more like a wrong decision.
AFAIK, decorations are just this border around the window, with the minimize, maximize, close and maybe roll up/down buttons.
Also, remember when a lot of people said "Linux is ugly and inconsistent"? Well, that's those days again, if you mandate it. Enabling it is an option, but using server side decorations by default is the way to go, IMO, and that's one of the few things I do like about KDE.
Also, yes, they intentionally thrown out as much functionality as possible, and that's because the kitchen sink approach has been proved wrong with X.
CSD is like prometheus' fire, yes. We can make good or bad of it. The nice part is we decide. Respecting HIGs, Theming and design guidelines are a good way to do it, Gnome proved this. KDE could do this too, it is really not that hard. Or are you saying that app developers shouldn't have the right to decide and features must be done away with? That is sweet irony, I think. Gnome wants flexibility and features, KDE wants to be locked down.Also, remember when a lot of people said "Linux is ugly and inconsistent"? Well, that's those days again, if you mandate it. Enabling it is an option, but using server side decorations by default is the way to go, IMO, and that's one of the few things I do like about KDE.
Qt's "write once, deploy everywhere" should not be allowed to stop us from making the best possible Linux desktop AND reducing complexity. KDE can find other ways to make the same code behave differently.
Nice fairy tale. You need to understand the kwin approach. They want SSD because they don't trust the app developers. And I can't blame them when it comes to KDE. Sure KDE would screw up and add inconsistent theming and various fluffy themes. But you can't blame CSD, blame the bad culture of KDE. Enforce HIGs, themes, designs etc and you are good. The only difference between being constrained by server decorations and a design guideline is that one is code and the other is human. But this is all details. What matters is that KDE wants to add complexity to wayland because they don't want the decoration complexity in the app code. And that is just wrong. App code is self contained, protocols are common domain.You have that exactly backwards. Gnome is the one trying to decide that app developers have to do away with certain features and do things exactly the same way. KDE wants sensible defaults, but allows applications to override them (just as they do right now).
Last edited by Honton; 08-15-2013 at 05:28 AM.