--===============8549601349128200117==
Content-Type: multipart/signed; boundary="nextPart4979483.r2lTKtySzR"; micalg="pgp-sha1"; protocol="application/pgp-signature"


--nextPart4979483.r2lTKtySzR
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

On Wednesday 26 February 2014 16:42:56 Thomas L=C3=BCbking wrote:
> On Mittwoch, 26. Februar 2014 16:27:47 CEST, Hugo Pereira Da Costa wr=
ote:
> > Note: a disable state could be quite easily added to oxygen. I
> > would reuse the same appearance as for inactive windows, except
> > that the button would stay 'inactive' even for active windows,
> > and would of course not highlight on mouse-over.
> > That's quite easy to implement, also.
> >=20
> > What do you think ?
>=20
> It's been one of the major religious wars about titlebars: what to do=
 with
> (temporarily) unsupported buttons.
>=20
> Personally, i LARGELY favor the approach where the button layout rema=
ins the
> same and a unusable button (cannot eg. maximize/minimize) is simply
> represented deactivated, but KDE has by default always done different=
 (more
> like Windows, less like MacOS)
>=20
> Arguments are that there's no point in crowding the titlebar with a U=
I
> element that will likely never activate and on the other hand the sta=
ble
> layout is more "reliable" for the user ("the outer right button is al=
ways
> maximize and not suddenly close")

I'm extending the discussion to the complete desktop to get some furthe=
r ideas=20
on whether we should change the behavior in 5.0.

For the Plasma devs: if a window is not closeable (or minimizeable or=20=

whatever) KWin is currently hiding the button. The alternative would be=
 to=20
have it always present but disabled if the action is not available.

Personally I think it's highly questionable that we remove the buttons =
as that=20
means the UI is inconsistent. On some windows there is one, on others t=
here is=20
none which can result in incorrect clicks and unexpected behavior. It's=
 also=20
very uncommon with respect to other elements. We don't hide the Apply b=
utton=20
if there is nothing to Apply, instead we deactivate it.

So IMHO we should use the chance of the major release and change our be=
havior=20
to not hide the buttons but disable them with the exception of the help=
 button=20
which would just clutter the UI.

Cheers
Martin
--nextPart4979483.r2lTKtySzR
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)

iEYEABECAAYFAlMPDJwACgkQqVXwidMiVrpBiQCeIw/CbUbqpRagxe3jGYn6F3/I
70cAoItmNyMgxUmF6Nr4I57ESLDLt2+1
=rRGZ
-----END PGP SIGNATURE-----

--nextPart4979483.r2lTKtySzR--


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

_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

--===============8549601349128200117==--