<html>
<body>
<div style="font-family: Verdana, Arial, Helvetica, Sans-Serif;">
<table bgcolor="#f9f3c9" width="100%" cellpadding="12" style="border: 1px #c9c399 solid; border-radius: 6px; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tr>
<td>
This is an automatically generated e-mail. To reply, visit:
<a href="https://git.reviewboard.kde.org/r/118946/">https://git.reviewboard.kde.org/r/118946/</a>
</td>
</tr>
</table>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<p style="margin-top: 0;">On June 26th, 2014, 9:29 a.m. CEST, <b>Thomas Lübking</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">this is however not ABI relevant, so depending on schedules one *could* wait for some specified NETWM hint (to not cruft the lib with the gtk+ prop symbol: removing it from the enum is oc. not API stable, thus not possible) and be introduced even with KWin 5.0.3 or whatever the final name scheme will be ;-)</pre>
</blockquote>
<p>On June 26th, 2014, 9:32 a.m. CEST, <b>Martin Gräßlin</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">yeah I'm fine with delaying to post 5.0 in frameworks. Means KWin 5.0 will not have full support for it. But if it gets into KWindowSystem 5.1 we can still add it in a minor KWin relase (and get killed by distros for increasing requirement in a minor release :-P ).</pre>
</blockquote>
<p>On June 26th, 2014, 9:53 a.m. CEST, <b>Thomas Lübking</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">if this is causing downstream dep issues, maybe a generic NETRootInfo::setSupported(const QString property) might be a good idea?</pre>
</blockquote>
<p>On June 26th, 2014, 10:01 a.m. CEST, <b>Martin Gräßlin</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">could be something to look into for 5.1, good idea.</pre>
</blockquote>
<p>On November 29th, 2014, 8:41 p.m. CET, <b>David Edmundson</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;"><p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">5.1 has been and gone. What's the status of this?</p></pre>
</blockquote>
<p>On November 29th, 2014, 9:27 p.m. CET, <b>Thomas Lübking</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;"><p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">There hasn't even been a request from gtk+ devs to get this into NETWM.
I was about to rant that the GTK ("gnome first") devs give a damn about interoperability and expect to "run after us!", but google (wanted to be sure ;-) pushed up
http://people.freedesktop.org/~cbrill/dri-log//dri-devel-2014-05-08.log</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">"07:45 #wayland: < Jasper> mgraesslin, whenever I send mails to wm-spec-list I don't get any replies, so I stopped bothering"</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">"Jasper" is apparently the one who added support to mutter.</p>
<hr style="text-rendering: inherit;margin: 0;padding: 0;white-space: normal;border: 1px solid #ddd;line-height: inherit;" />
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">@Martin
I would suggest to either declare NETWM dead XOR formalize the board.</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">Eg. one would define a "high council" consisting of the maintainers of the relevant™ WMs (KWin, Mutter, Openbox and Enlightenment for sure. Compiz IFFFFFF Canonical promises to behave. Eventually awesome? I probably forgot an obvious one) an setup some rules.</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">a) A proposal of a high council member w/o veto of any other HC member within 21 days is in.
b) A proposal of a non member that has seen no reaction from high council or delegates within 21 days causes reposts with increasing frequence.
c) New features MUST be announced as supported by the WM, ignoring that hint and just expecting it is a client bug by definition.
d) A proposal containing the term "should" or any equivalent is auto-invalid ;-)</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">I'd also suggest to move from wm-spec-list@gnome.org to sth. like netwm@lists.freedesktop.org and/or have a fdo bugzilla bugtracker for handling concerns/proposals.</p></pre>
</blockquote>
</blockquote>
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;"><blockquote style="text-rendering: inherit;padding: 0 0 0 1em;border-left: 1px solid #bbb;white-space: normal;margin: 0 0 0 0.5em;line-height: inherit;">
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">5.1 has been and gone. What's the status of this?</p>
</blockquote>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">it's an insufficient solution. There are a bazillion of issues which need to be addressed like
<em style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: normal;"> button position order
</em> geometries of each button (we need to know the position of the close button to recognize a failed attempt to close the window)
* ...</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">This is just a part of the overall puzzle and I had tried to take it to the NETWM spec list, but hadn't had the momentum to complete the process (after all I have zero interest in fixing behind GTK). It's a lot of work and honestly I think it's a wasted effort as GTK should do the sane thing and disable their decorations on other desktops.</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">Nevertheless we should make sure that these things will be done properly in the XdgShell for Wayland. Jasper is the main developer of the protocol and I consider him cooperative. I plan to look on the protocol sometime soon and prepare a "KDE view" on it. In my opinion most things missing are related to decorations (e.g. button ordering, etc.). I'll also try to get once again an agreement on that we need to be able to disable decorations completely for convergence. On second thought: it might be better some other KDE dev proposes this not to run into it being ignored because I'm a known opponent of CSD.</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">For this particular item: if we want to add support we should do it in KWin, but again: I don't care.</p></pre>
<br />
<p>- Martin</p>
<br />
<p>On June 26th, 2014, 9:22 a.m. CEST, Martin Gräßlin wrote:</p>
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="12" style="border: 1px #888a85 solid; border-radius: 6px; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tr>
<td>
<div>Review request for KDE Frameworks and kwin.</div>
<div>By Martin Gräßlin.</div>
<p style="color: grey;"><i>Updated June 26, 2014, 9:22 a.m.</i></p>
<div style="margin-top: 1.5em;">
<b style="color: #575012; font-size: 10pt;">Repository: </b>
kwindowsystem
</div>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Description </h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" style="border: 1px solid #b8b5a0">
<tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Adding property _GTK_SHOW_WINDOW_MENU to NET::Properties2
Although non-standard it needs to be added to the NET::PRoperties2
in order to have KWin announce it in the supported section.
As soon as this gets standardized WM2ShowWindowMenu can be changed
to point to both the proprietary GTK hint and the standardized hint.</pre>
</td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Diffs</b> </h1>
<ul style="margin-left: 3em; padding-left: 0;">
<li>autotests/netrootinfotestwm.cpp <span style="color: grey">(f8c28be51e5a5b19d436c54eede0e8659a65c84e)</span></li>
<li>src/netwm.cpp <span style="color: grey">(1daad1e5fc87fa85da6348a059d0ae0acec26eaf)</span></li>
<li>src/netwm_def.h <span style="color: grey">(0edadc085e08531ec81bcde5651e8475e8573091)</span></li>
</ul>
<p><a href="https://git.reviewboard.kde.org/r/118946/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>