Re: Proposal: Add a window state for "undecorated" windows

--===============8110986062709320124==
Content-Type: multipart/alternative; boundary=001a1133d54e83e9f504f2d948ab

--001a1133d54e83e9f504f2d948ab
Content-Type: text/plain; charset=ISO-8859-1

I guess I'm curious then, what's the goal? What does this provide beyond
the Motif hint?

If it's "nothing, it's just standardizing it", then I'm against it. CSD
requires a complete solution, and I'd rather see a complete solution
standardized than a slightly-less-bad Motif hint.

I could add support in mutter for the new state, but I wouldn't port GTK+
to it. The Motif hint has wider reach across a wide pool of existing WMs,
and we'd just be regressing for no real gain. Not to mention that on WMs
without support for client-set frame extents, we keep the "border" hint on
so that users can resize the window through the WM-provided borders, even
if they don't get a server-side titlebar.


On Thu, Feb 20, 2014 at 11:38 AM, Martin Graesslin <[email protected]>wrote:

> On Thursday 20 February 2014 10:23:41 Jasper St. Pierre wrote:
> > There's a bunch of open questions about this state. If a window is
> > CSD-drawn, does it include drop-shadows, or should the compositor draw
> > drop-shadows?
>
> thanks for the feedback. I think there is a small misunderstanding in what
> I
> wanted to achieve with the proposal. It's not to come up with the ultimate
> way
> to handle CSD - I think it's obvious that I'm the wrong person to propose
> that
> ;-)
>
> The idea is really just to make a modern way for the motif hint. Whether or
> how CSD styling is done is IMHO completely orthogonal. Especially the
> consideration of shadows is something which has nothing to do with whether
> the
> window is decorated or not. The hint to not decorate the window is clearly
> relevant for the window manager and the styling is clearly relevant to the
> compositor. Thus it addresses two completely different parts and should
> IMHO
> not be mixed.
>
> Cheers
> Martin
>
> _______________________________________________
> wm-spec-list mailing list
> [email protected]
> https://mail.gnome.org/mailman/listinfo/wm-spec-list
>
>


-- 
  Jasper

--001a1133d54e83e9f504f2d948ab
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I guess I&#39;m curious then, what&#39;s the goal? Wh=
at does this provide beyond the Motif hint?<br><br></div><div>If it&#39;s &=
quot;nothing, it&#39;s just standardizing it&quot;, then I&#39;m against it=
. CSD requires a complete solution, and I&#39;d rather see a complete solut=
ion standardized than a slightly-less-bad Motif hint.<br>

<br></div><div>I could add support in mutter for the new state, but I would=
n&#39;t port GTK+ to it. The Motif hint has wider reach across a wide pool =
of existing WMs, and we&#39;d just be regressing for no real gain. Not to m=
ention that on WMs without support for client-set frame extents, we keep th=
e &quot;border&quot; hint on so that users can resize the window through th=
e WM-provided borders, even if they don&#39;t get a server-side titlebar.<b=
r>

</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">O=
n Thu, Feb 20, 2014 at 11:38 AM, Martin Graesslin <span dir=3D"ltr">&lt;<a =
href=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a>=
&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"">On Thursday 20 February 2014=
 10:23:41 Jasper St. Pierre wrote:<br>
&gt; There&#39;s a bunch of open questions about this state. If a window is=
<br>
&gt; CSD-drawn, does it include drop-shadows, or should the compositor draw=
<br>
&gt; drop-shadows?<br>
<br>
</div>thanks for the feedback. I think there is a small misunderstanding in=
 what I<br>
wanted to achieve with the proposal. It&#39;s not to come up with the ultim=
ate way<br>
to handle CSD - I think it&#39;s obvious that I&#39;m the wrong person to p=
ropose that<br>
;-)<br>
<br>
The idea is really just to make a modern way for the motif hint. Whether or=
<br>
how CSD styling is done is IMHO completely orthogonal. Especially the<br>
consideration of shadows is something which has nothing to do with whether =
the<br>
window is decorated or not. The hint to not decorate the window is clearly<=
br>
relevant for the window manager and the styling is clearly relevant to the<=
br>
compositor. Thus it addresses two completely different parts and should IMH=
O<br>
not be mixed.<br>
<br>
Cheers<br>
<span class=3D"HOEnZb"><font color=3D"#888888">Martin<br>
</font></span><br>_______________________________________________<br>
wm-spec-list mailing list<br>
<a href=3D"mailto:[email protected]">[email protected]</a><br>
<a href=3D"https://mail.gnome.org/mailman/listinfo/wm-spec-list" target=3D"=
_blank">https://mail.gnome.org/mailman/listinfo/wm-spec-list</a><br>
<br></blockquote></div><br><br clear=3D"all"><br>-- <br>=A0 Jasper<br>
</div>

--001a1133d54e83e9f504f2d948ab--

--===============8110986062709320124==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
wm-spec-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/wm-spec-list

--===============8110986062709320124==--