--===============2057724950==
Content-Type: multipart/signed; boundary="nextPart1404947.bPBnOlnCqn"; micalg="pgp-sha1"; protocol="application/pgp-signature"
Content-Transfer-Encoding: quoted-printable


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

Hi all,

thanks you two for clarifying some parts. Overall that sounds rather go=
od what Aur=C3=A9lien=20
writes and I think dbusmenu is suited for the task. Personally I am ver=
y surprised be the echo=20
this idea created - no other blog post has received so many and so many=
 positive comments=20
in so short time. This shows me that it's worth to spend time on it, bu=
t I think it makes sense to=20
delay to 4.8.

On Wednesday 30 March 2011 15:31:02 Thomas L=C3=BCbking wrote:
<snip>
> We could have derived and explicitly restricted classes for the dbusm=
enu =20
> support.
> This would ensure only "proper" menus are handled but would of course=
 =20
> cause some transition time.
I think that is the only way to go. Looking at what Peter Penz did for =
Dolphin and what Firefox=20
does when dropping to one menu, it strikes me that we cannot put a norm=
al menu into the=20
deco. That will be unusable.

Therefore there is one clear path: get support into KWin and Deco and n=
egotiate with the=20
windows if they want to put a menu into the deco and let the windows pr=
ovide their special=20
menu for this usecase. That might also be a solution for the topmenu wh=
en dropping into a=20
button btw. So what we need is probably an additional property to annou=
nce that the WM=20
supports adding menus to the deco and for the windows to specify that t=
hey want to provide=20
a menu. If a window does not provide, it is classic in the window.

Oh and looks like we need a KDecoration3.
>=20
> If on the other hand one just drops the dbusmenu on top of the existi=
ng =20
> qmenu world (and esp, from a platform plugin etc. which will alos cov=
er =20
> proprietary 3rd party applications), i'm willing to bet =20
> [awholebigbunchofbucks] to get at least one more break/"needs patchin=
g =20
> case" - likely more.
Following the Linux kernel: never break your downstreams :-)
--nextPart1404947.bPBnOlnCqn
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEABECAAYFAk2TesUACgkQqVXwidMiVroRqwCdFE9MavtzP+rU4Nf13tkLafIy
YoAAnRGlKTlnzMT0s2kV/j8+hSoJIuE5
=2HdC
-----END PGP SIGNATURE-----

--nextPart1404947.bPBnOlnCqn--


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

_______________________________________________
kwin mailing list
kwin@kde.org
https://mail.kde.org/mailman/listinfo/kwin

--===============2057724950==--