Announcement
Collapse
No announcement yet.
GNOME Display Settings Now Working On Wayland
Collapse
X
-
Originally posted by Awesomeness View PostI watched the Wayland talk from last year's X conference. The ?compelling? reason given for CSD was:
When you rotate a window, you won't get a single jagged pixel line between titlebar and window content.
But the reality is:
No one rotates windows and even if one did, nobody would care about a single line of pixels.
Thing is, however, the disadvantage of SSD can be overcome by merging the surfaces into one surface before transformation, but this of course requires one extra operation - however, if you have the extra power available to wobble your windows, I don't think it's much of a concern.
Comment
-
Originally posted by dee. View PostDefault to CSD, but if the client wants to use SSD, it can just request the compositor to "draw me a simple decoration".
Comment
-
Originally posted by mrugiero View PostSo, default to what is used in corner cases. I don't think that's the best idea. Specially because this implies the ones who doesn't care about decorations still need to place code to handle decorations.
Comment
-
But isn't this whole discussion academic, anyway? Any Wayland compositor has to support SSD for one simple reason: xwayland. xwayland requires SSD. So any compositor that supports xwayland will need to have SSD support.
Weston already supports SSD for this reason. It is currently in the xwayland source, which means it is only exposed to xwayland clients, but the code is all there.
Comment
-
Originally posted by Awesomeness View Post
In my opinion the default should be whatever the application wants, but the user or the window manager should be able to switch to SSD. Otherwise things like unity or plasma active aren't possible.
Comment
-
Originally posted by Maxjen View PostNot the same thing. For example you can't have shortcuts like ctrl+t to open new tabs.Last edited by TheBlackCat; 18 August 2013, 06:30 PM.
Comment
-
Originally posted by TheBlackCat View PostBut isn't this whole discussion academic, anyway? Any Wayland compositor has to support SSD for one simple reason: xwayland. xwayland requires SSD. So any compositor that supports xwayland will need to have SSD support.
Weston already supports SSD for this reason. It is currently in the xwayland source, which means it is only exposed to xwayland clients, but the code is all there.
Originally posted by Maxjen View PostIn my opinion the default should be whatever the application wants, but the user or the window manager should be able to switch to SSD. Otherwise things like unity or plasma active aren't possible.
Originally posted by dee. View PostThey already need to place code to open windows on the screen. Having to call one extra function with arguments to the effect of "draw me decorations with this title text and these buttons" isn't really anything more than they'd have to do in a SSD-by-default model, either.
I think we agree that both should be supported and a sane default should be applied, along with two switches, one for the application to choose what it wants, and one for the user to override application's decisions, and I think that's the most important part. The other point is just a matter of preference, and I don't think it changes greatly the outcome.
Comment
-
Originally posted by mrugiero View PostYes. But it's still something not needed, and by basic logic, using custom decorations (the main advantage, IMO, of CSD) you'll need to place extra code, so an extra function call to state you'll use CSD makes more sense there.
Heck, the function call for CSD and SSD apps could even be the same:
create_window(USE_SSD, title_text, button_configuration);
vs.
create_window(USE_CSD);
doable with varargs.
I think we agree that both should be supported and a sane default should be applied, along with two switches, one for the application to choose what it wants, and one for the user to override application's decisions, and I think that's the most important part. The other point is just a matter of preference, and I don't think it changes greatly the outcome.
Comment
-
Originally posted by Teho View PostCould you list them or point where those are explained?
Originally posted by Awesomeness View PostI watched the Wayland talk from last year's X conference. The ?compelling? reason given for CSD was:
When you rotate a window, you won't get a single jagged pixel line between titlebar and window content.
But the reality is:
No one rotates windows and even if one did, nobody would care about a single line of pixels.
Comment
Comment