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.
 
 
 
 
Jochen Friedrich b075a7c4cb Initial commit 10 years ago
introspection Initial commit 9 years ago
src Initial commit 9 years ago
test Initial commit 9 years ago
.gitignore Initial commit 9 years ago
AUTHORS Initial commit 9 years ago
ChangeLog Initial commit 9 years ago
Makefile.am Initial commit 9 years ago
NEWS Initial commit 9 years ago
README Initial commit 9 years ago
autogen.sh Initial commit 9 years ago
configure.in Initial commit 9 years ago
de.bocc.ClewareManager.conf Initial commit 9 years ago
de.bocc.ClewareManager.service.in Initial commit 9 years ago

README

ClewareManager.
The problem ClewareManager tries to solve is to provide a unified high level API
for communicating with cleware devices.

Using.
ClewareManager is a system daemon and is not meant to be used directly from
the command line. However, since it provides DBus API, it is possible to use
'dbus-send' command to control it from the terminal. There's an example
program (tests/cleware-test.py) that demonstrates the basic API usage.

Implementation.
ClewareManager is a DBus system bus activated service (meaning it's started
automatically when a request arrives). It is written in C. The devices are
queried from udev and automatically updated based on hardware events.

API.
The API is open for changes, so if you're writing a plugin and need to add or
change some public method, feel free to suggest it!