From kde-core-devel  Fri Apr 29 23:24:00 2005
From: "Aaron J. Seigo" <aseigo () kde ! org>
Date: Fri, 29 Apr 2005 23:24:00 +0000
To: kde-core-devel
Subject: Re: Thoughts on the systray II.
Message-Id: <200504291724.15423.aseigo () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=111481735625292
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart1236354.kL4HjxIMMW"

--nextPart1236354.kL4HjxIMMW
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Friday 29 April 2005 12:36, Kuba Ober wrote:
> > the particular reason here is that there is no one-to-one relationship
> > between windows and systray icons. nor should there need to be. the app
> > should be able to create as many or as few as it wants, regardless of h=
ow
> > many windows it's showing.
>
> Methinks that ideally, one should be able to write a "plain old C"
> application that shows itself in the systray, assuming that C bindings to
> whatever IPC is being used are available. And that application ideally
> should not depend on X libraries.

agreed. for now we can experiment with it using WM hints until we get the=20
interaction down, and then when we move to an IPC mechanism with a system b=
us=20
we can switch to that =3D)

=2D-=20
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

--nextPart1236354.kL4HjxIMMW
Content-Type: application/pgp-signature

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

iD8DBQBCcsIf1rcusafx20MRAmbOAJsEFepdVBMdiZ+lnD6PYsXQXfFnbACeNWMB
wI/kglQUn80DEmMkUeTMCsA=
=LhDo
-----END PGP SIGNATURE-----

--nextPart1236354.kL4HjxIMMW--