From kde-core-devel  Mon Jun 02 20:13:00 2003
From: Gav Wood <gav () indigoarchive ! net>
Date: Mon, 02 Jun 2003 20:13:00 +0000
To: kde-core-devel
Subject: Re: new kde project
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=105461826121427
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--Boundary-02=_Q/62+Hx8C1aAjtj"


--Boundary-02=_Q/62+Hx8C1aAjtj
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline

> Yes, there are more devices than just IR remote controls that could benef=
it
> from the infrastructure:
> - multimedia keyboards (PS/2 or USB, driven by keycodes)
> - USB HID devices (like the 'copy' buttons on scanners and 'snapshot' on
> webcams)
> - bluetooth remote controls (there are specal bluetooth devices to control
> presentations, so you would have commands like 'next slide')

add hot plug events to that.

this is all thue, however i'm not sure how extensive the khotkeys architect=
ure=20
is to allow such a generalised mapping; a plugin architecture seems like it=
=20
should be considered for input events at least.

the architecture would have to support several new (to khotkeys) concepts=20
including having multiple devices from a single plugin capable of sustainin=
g=20
their own states.

> I also wonder how it interacts with other IR software: while this IR
> handler is running, is it still possible to receive other data, for examp=
le
> using OBEX?

all other ir-rc software works fine - lirc provides a character device=20
/dev/lirc, which any number of applications may connect to to receive ir-rc=
=20
events.
i'm not sure how this releates to obex or irda in general. i suspect they h=
ave=20
no effect on each other unless they use the same hardware, in which case i=
=20
suspect they're mutually exclusive. pure speculation though.

gav
=2D-=20
Gav Wood <gav@indigoarchive.net>

codito ergo non satis bibivi

--Boundary-02=_Q/62+Hx8C1aAjtj
Content-Type: application/pgp-signature
Content-Description: signature

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

iD8DBQA+26/Q7nE5x1pIEBQRAt69AJ9Z8huqy5C4INEnimZsLwDedihj9gCeK1OT
EWK0v2cQH2nGnV7b3XM4C78=
=iRQK
-----END PGP SIGNATURE-----

--Boundary-02=_Q/62+Hx8C1aAjtj--