<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 08/08/2022 09:05, JiDe Zhang wrote:<br>
</div>
<blockquote type="cite"
cite="mid:PH0PR02MB74956F800CC0068B575EEEEBD8639@PH0PR02MB7495.namprd02.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<style type="text/css" style="display:none;">P {margin-top:0;margin-bottom:0;}</style>
<div style="font-family: Calibri, Helvetica, sans-serif;
font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Hi:</div>
<div style="font-family: Calibri, Helvetica, sans-serif;
font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif;
font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Is it that more people think that not allowed the window to set
their position is better? I think that Wayland is better than
X11 In this regard. It is correct to not let the window be set
position, But some people will have doubts, because their know
that some windows need to set their own position. We should pay
attention to these needs and analyze what is the real reason
their need for this interface,</div>
</blockquote>
<p><br>
</p>
<p>It is entirely understandable for the designers of applications
and application toolkits to be surprised they don't have the
control they have in other windowing systems (X11, Windows,
whatever). For decades they've been used to deciding where their
windows go. Trusting the compositor to do that is a surprise.<br>
</p>
<p><br>
</p>
<p>But in the real world, they have to conform to a small number
idioms that users recognise, and supporting those is very possible
without allowing "full control". We've done some work on
classifying these idioms for Mir and there's a presentation of our
findings here:</p>
<p><br>
</p>
<p><a moz-do-not-send="true"
href="https://mir-server.io/docs/window-positions-under-wayland"
class="moz-txt-link-freetext">https://mir-server.io/docs/window-positions-under-wayland</a></p>
<p><br>
</p>
<p>The tl;dr is that most of the idioms (regular windows, dialogs,
menus, popus, tooltips, hovers, satellites, toolboxes) are already
supported and there's no fundamental problem extending the
existing approach used by Wayland to cover others. (Most of the
support needed can be cut & paste from other idioms.)<br>
</p>
</body>
</html>