TDE utility programs
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Slávek Banko b243598f2e
Move the tdelirc manuals to the directory level in which they are installed.
1 week ago
..
icons Fix invalid headers in PNG files and optimize for size 4 years ago
irkick Simplify CMake rules for desktop file translations. 4 months ago
kcmlirc Move the tdelirc manuals to the directory level in which they are installed. 1 week ago
profiles Rename kdessh -> tdessh and kdelirc -> tdelirc. 7 years ago
remotes Rename kdessh -> tdessh and kdelirc -> tdelirc. 7 years ago
tdelirc Add CMakeL10n rules. 1 year ago
AUTHORS Rename kdessh -> tdessh and kdelirc -> tdelirc. 7 years ago
CMakeL10n.txt Desktop file translations: 6 months ago
CMakeLists.txt Rename kdessh -> tdessh and kdelirc -> tdelirc. 7 years ago
COPYING Rename kdessh -> tdessh and kdelirc -> tdelirc. 7 years ago
ChangeLog Fix incorrectly moved kdelirc files 7 years ago
Makefile.am Rename kdessh -> tdessh and kdelirc -> tdelirc. 7 years ago
README Rename kdessh -> tdessh and kdelirc -> tdelirc. 7 years ago
README.profile-creation Rename kdessh -> tdessh and kdelirc -> tdelirc. 7 years ago
README.remote-creation Rename kdessh -> tdessh and kdelirc -> tdelirc. 7 years ago
TODO Rename kdessh -> tdessh and kdelirc -> tdelirc. 7 years ago

README

tdelirc
-------

TDELIRC is a TDE frontend for the Linux Infrared Remote Control system. It has
two aims:

1. Provide a control center module for configuration of:
a) Application bindings to remote control buttons.
b) Actual remote controls installed (i.e. lirc configuration).

2. Provide a system-tray applet to act as a proxy between the LIRC system and
TDE (applications), in order to launch DCOP requests (and potentially
other IPC signals) to applications (and potentially collect/display
results).

INSTALLATION

Nothing but the normal ./configure && make && su -c "make install".

SETUP

For the TDELirc system to work properly, you *must* have lircd configured and
running. If you have already had a Lirc program running, then you most likely
have Lirc set up properly. If not, be sure that you have a correct kernel module
loaded for your IR receiver (1) and that the lircd program is running (2).

You must also have some remote controls configured in "/etc/lircd.conf". Go to
the lircd website (www.lirc.org) for more information on this.

(1) /sbin/lsmod | grep lirc
If you see some output, you have a lirc kernel module loaded (that's not to say
it's the right module for your hardware).

(2) ps aux | grep -v grep | grep lircd
If you see some output, you have the lircd program running. This is good.

DESIGN

The design of the system is really quite simple---a control center module
modifies a centralised configuration file to determine what action(s) should
be taken on a remote control's button press.

The same(?) module also provides a front-end for the input of /etc/lircd.conf,
necessary to specify remote controls to the LIRC system. An extra (standard
format XML-based) may be provided with the remote control description to give
less sucky (lower case, no spaces/symbols) names.

The /etc/lircd.conf frontend has not yet been implemented, though all other
features are.

The system tray applet interfaces with LIRC in order to catch key presses on
remote controls. It is then able to communicate with and potentially start
applications through DCOP.

Gav Wood, 2003 (gav at kde dot org).