From kde-core-devel  Fri Jun 06 00:19:35 2003
From: Gav Wood <gav () kde ! org>
Date: Fri, 06 Jun 2003 00:19:35 +0000
To: kde-core-devel
Subject: Re: new kde project
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=105485891002482
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--Boundary-02=_b493+Q46g+epLHJ"


--Boundary-02=_b493+Q46g+epLHJ
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline

> Anyway, if the general opinion is putting it in kdeutils, I'm ok with tha=
t,
> as long as someone adds a way to quit irkick and restart it.

since it's a kded service, to restart it all you have to do is go into=20
kcontrol and under service manager select the lirc entry and press the stop=
=20
button, followed by the start button.

this doesn't allow you to tell the cpu usage, but its job is such that it=20
would be highly unlikely to cause any sort of cpu usage on anything higher=
=20
than a 386 --- if you really wanted to test it you could disable all other=
=20
kded services, wait for a quiet time when kded wouldn't be doing anything b=
y=20
itself and start using irkick.

the reason i coded it as a plugin (aside to allow more transparent integrat=
ion=20
with kde) was to allow inbuilt starting of the service (and it *is* a=20
service) as kde starts up; putting it in the Autostart folder or whatever=20
just doesn't seem a correct or elegant solution. i'm actually quite pleased=
=20
with the integration, especially compared to how it was when it was a progr=
am=20
on its own.

gav

ps kdelibs sounds ok :-)
=2D-=20
Gav Wood <gav@kde.org>

codito ergo non satis bibivi

--Boundary-02=_b493+Q46g+epLHJ
Content-Type: application/pgp-signature
Content-Description: signature

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

iD8DBQA+394b7nE5x1pIEBQRAplKAKC0tOyy6DxyIka7ovmdg5q9W83YxACgslQx
boq4sL30Bg5WNzwE0jE5saQ=
=9dY2
-----END PGP SIGNATURE-----

--Boundary-02=_b493+Q46g+epLHJ--