From kde-core-devel  Fri May 09 02:55:48 2014
From: Thiago Macieira <thiago () kde ! org>
Date: Fri, 09 May 2014 02:55:48 +0000
To: kde-core-devel
Subject: Re: Compatibility problems with latest GTK+ applications
Message-Id: <16767328.BpxLbPWCEu () tjmaciei-mobl4>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=139960420217793
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart1730930.Cfm5fkcZYR"


--nextPart1730930.Cfm5fkcZYR
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"

Em qui 08 maio 2014, =E0s 15:01:10, Martin Gr=E4=DFlin escreveu:
> On Thursday 08 May 2014 14:39:49 Matthias Klumpp wrote:
> > 2014-05-08 9:31 GMT+02:00 Martin Gr=E4=DFlin <mgraesslin@kde.org>:
> > > * CSD styled windows don't react on compositing changes [1]
> > > * Double decorated windows [2]
> > > * CSD styled windows do not detect when re-parented to a decorati=
on [3]
> > > * CSD context menu ignores _NET_ALLOWED_ACTIONS [4]
> > > * CSD context menu doesn't use _NET_DESKTOP_NAMES [5]
> > > * CSD context menu doesn't honor _NET_DESKTOP_LAYOUT [6]
> > > * Shadow included in CSD window [7]
> > > * Window "disappears" when middle clicking client side decoration=
 [8]
> > > * Missing maximize and minimize buttons in client side decoration=
 [9]
> > > * Decoration buttons do not follow custom specified layout in des=
ktop
> > > environment [10]
> > > * A hung GTK application cannot be closed [11]
> > > * Context menu on window decoration is not the one of the environ=
ment
> > > [12]
> > > * No time based drag delay on window moving [13]
> > > * No drag delay on window resize [14]
> >=20
> > That is pretty great, thank you for taking the time! Some of these
> > things unfortunately are design-decisions by GNOME, which I raised =
in
> > IRC discussions a while ago, and where I think the interest is pret=
ty
> > low for fixing them (after getting some feedback on e.g. the CSD
> > menus).
>=20
> which of the bug reports do you consider affected by design-decisions=
? I did
> not even report the mismatching cursors and the missing close button =
for
> dialogs and similar things.

I'd say at least 11, 12. A design decision of any CSD is that the clien=
t=20
controls its closing and, therefore, if the client is hung, you can't t=
ell it=20
to close. You can kill the application with kill, xkill or using a glob=
al=20
shortcut (Alt+F4, Ctrl+Alt+Esc, etc.) As for the context menu, it can b=
e said=20
it's part of the themeing: the CSD application needs to get information=
 from=20
the desktop in order to draw the proper decorations. You could say that=
=20
includes what the context menu should look like.

That said, I fully expect 4, 6, 9, 13 and 14 to be also closed as "work=
ing as=20
designed" because of the UX decisions. That is, "we think this dialog=20=

shouldn't have a close button, so we won't draw it, despite what the de=
sktop=20
says".
=2D-=20
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

--nextPart1730930.Cfm5fkcZYR
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iD8DBQBTbEPDM/XwBW70U1gRAoEQAJ9GjmiTN0q10Oteu3rTqC3QQ1DSOwCfeG3h
L3wQype6vsZowWPK9NvQd2A=
=El9J
-----END PGP SIGNATURE-----

--nextPart1730930.Cfm5fkcZYR--