All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aivils <aivils@unibanka.lv>
To: linux-kernel@vger.kernel.org, kde-linux@mail.kde.org,
	post-only@gnome.org, xfree86@XFree86.Org, xorg@freedesktop.org
Cc: linuxconsole-dev@lists.sourceforge.net, Vojtech Pavlik <vojtech@suse.cz>
Subject: Multimedia key utilization under Linux. Another implementation.
Date: Wed, 1 Dec 2004 10:31:55 +0300	[thread overview]
Message-ID: <200412010931.55053.aivils@unibanka.lv> (raw)

Hi All!

X - X windows system
K - Linux kernel
E - Events as well

INTRODUCTION
------------

    xke is userspace program which is capable read and recognize Linux
kernel generated events of input devices. xke translate Linux kernel
events and send to X windows system. Main goal is keyboar multimedia key
utilization.
    As input xke uses /dev/input/eventXX device files. As output xke uses
Xtst.so library alias Xtest extension.
    xke uses unified Linux input event system. xke don't care what input
device is connected in the box. From point of view of xke differs only
device name and some parmeters. So xke satisfactory works with keyboard,
mouse and tablet.
    xke can connect to local X server any time when end-user will do it,
because use Xtst library. End-user may start and stop xke during X sesion
and use user specific settings.
    Right now xke maps key press/release events to
generate key (key-press/release) series
launch programs
generate mouse motions
generate button-press/release
    Button press and x y axis motion events will be sended to X "unchanged".

xke is a merge and rewrite from the programs:
evdev XFree86 driver by Zephaniah E. Hull
xkeymouse by Henrik Sandklef
tuntiko XFree86 driver by Daniel Skarda

http://www.ltn.lv/~aivils/files/xke-0.01.tar.bz2

Best regards, Aivils Stoss

                 reply	other threads:[~2004-12-01  7:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200412010931.55053.aivils@unibanka.lv \
    --to=aivils@unibanka.lv \
    --cc=kde-linux@mail.kde.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxconsole-dev@lists.sourceforge.net \
    --cc=post-only@gnome.org \
    --cc=vojtech@suse.cz \
    --cc=xfree86@XFree86.Org \
    --cc=xorg@freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.