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.
|
12 years ago | |
---|---|---|
introspection | 12 years ago | |
src | 12 years ago | |
test | 12 years ago | |
AUTHORS | 15 years ago | |
ChangeLog | 15 years ago | |
Makefile.am | 12 years ago | |
NEWS | 15 years ago | |
README | 12 years ago | |
autogen.sh | 15 years ago | |
configure.in | 12 years ago | |
de.bocc.MissileManager.conf | 12 years ago | |
de.bocc.MissileManager.service.in | 12 years ago |
README
MissileManager.
The problem MissileManager tries to solve is to provide a unified high level API
for communicating with missile launchers. While the hardware and functions are
similar, the protocol to control the missile launcers (like moving around, fire
missile) varies a lot.
Using.
MissileManager 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/missile-test.py) that demonstrates the basic API usage.
Implementation.
MissileManager 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!