3
part of the KDE project.
5
Copyright: 2009 - 2010 Michael Zanetti <michael_zanetti@gmx.net>
6
2009 - 2010 Frank Scheffold <fscheffold@googlemail.com>
8
Author/Maintainer: Michael Zanetti <michael_zanetti@gmx.net>
9
Author: Frank Scheffold <fscheffold@googlemail.com>
13
KRemoteControl is a KDE frontend for your remote controls. It allows to configure
14
actions for button presses on remotes. All types of remotes supported by
15
Solid are also supported by KRemoteControl. For usage instructions see
16
the KRemoteControl handbook provided with the kdeutils module.
19
KRemoteControl consists of the following modules:
21
This lib holds all the basic data structures for handling remotes,
22
modes and actions. Additionally it holds a D-Bus browser interface
23
and executors for actions.
26
This is the configuration module for systemsettings. It allows to
27
create and assign actions to remote controls.
30
A kded module responsible for actually executing the actions on incoming
34
A notifier item sitting in the notification area (aka system tray).
35
Its job is to notify the user of incoming button presses by blinking
36
and provides a context menu for manually switching a remotes mode.
39
This is a plasma dataengine. It allows to interact with the kded module
40
within a plasmoid. There is no plasmoid provided with KRemoteControl yet.
45
* To create new action templates you need to create a profile. See the
46
KRemoteControl handbook for a step by step guide.
48
* To add new types of supported remotes you need to create a new Solid
49
remote control backend.
51
* To add new types of actions you need to provide an Action class derived
52
from action, an executor able to execute your action and a configuration