MCPcopy Index your code
hub / github.com/libratbag/piper

github.com/libratbag/piper @0.8

Chat with this repo
repository ↗ · DeepWiki ↗ · release 0.8 ↗ · + Follow
311 symbols 775 edges 24 files 141 documented · 45% updated 2mo ago★ 5,865206 open issues
What it actually does AI analysis from the code graph — generated when you open this
loading…
README

Piper

Piper is a GTK+ application to configure gaming mice. Piper is merely a graphical frontend to the ratbagd DBus daemon, see the libratbag README for instructions on how to run ratbagd.

If you are running piper from git, we recommend using libratbag from git as well to make sure the latest bugfixes are applied.

Supported Devices

Piper is merely a frontend, the list of supported devices depends on libratbag. See the libratbag device files for a list of all known devices. The device-specific protocols usually have to be reverse-engineered and the features available may vary to the manufacturer's advertized features.

Screenshots

resolution configuration screenshot

button configuration screenshot

LED configuration screenshot

And if you see the mousetrap, something isn't right. Usually this means that either ratbagd is not running (like in this screenshot), ratbagd needs to be updated to a newer version, or some other unexpected error occured.

The error page

Installing Piper

See our Wiki for how to install Piper.

Building Piper from git

Piper uses the meson build system. Run the following commands to clone Piper and initialize the build:

git clone https://github.com/libratbag/piper.git
cd piper
meson builddir --prefix=/usr/

To build or re-build after code-changes and install, run:

ninja -C builddir
sudo ninja -C builddir install

Note: builddir is the build output directory and can be changed to any other directory name.

See our Wiki for what to do when you encounter missing dependencies.

Contributing

Yes please. It's best to contact us first to see what you could do. Note that the devices displayed by Piper come from libratbag.

For quicker development iteration, there is a special binary piper.devel that uses data files from the git directory. This removes the need to install piper after every code change.

ninja -C builddir
./builddir/piper.devel

Note that this still requires ratbagd to run on the system bus.

Piper tries to conform to Python's PEP8 style guide using the black formatter. Checking if code is formatted is done as a part of the test suite.

You can check if your code passes tests before submitting changes using the following command:

meson test -C builddir

Source

git clone https://github.com/libratbag/piper.git

Bugs

Bugs can be reported in the issue tracker on our GitHub repo: https://github.com/libratbag/piper/issues

License

Licensed under the GPLv2. See the COPYING file for the full license information.

Core symbols most depended-on inside this repo

_get_dbus_property
called by 37
piper/ratbagd.py
N_
called by 29
piper/ratbagd.py
_set_dbus_property
called by 19
piper/ratbagd.py
connect_signal_with_weak_ref
called by 17
piper/util/gobject.py
set_active
called by 14
piper/profilerow.py
_present_error_perspective
called by 9
piper/window.py
error
called by 9
tests/check-svg.py
add
called by 8
piper/mousemap.py

Shape

Method 253
Class 45
Function 12
Route 1

Languages

Python100%

Modules by API surface

piper/ratbagd.py116 symbols
piper/mousemap.py27 symbols
piper/buttondialog.py24 symbols
piper/mouseperspective.py20 symbols
piper/resolutionrow.py16 symbols
piper/window.py14 symbols
piper/welcomeperspective.py12 symbols
piper/advancedpage.py11 symbols
tests/check-svg.py10 symbols
piper/profilerow.py8 symbols
piper/leddialog.py8 symbols
piper/errorperspective.py8 symbols

For agents

$ claude mcp add piper \
  -- python -m otcore.mcp_server <graph>

⬇ download graph artifact