jdDBusDebugger 4.2
An advanced D-Bus Debugger
Requires Python: >=3.10
Keywords: JakobDev, Linux, DBus

<h1 align="center">jdDBusDebugger</h1>

<h3 align="center">An advanced D-Bus Debugger</h3>

<p align="center">
    <img alt="jdDBusDebugger" src="screenshots/MainWindow.png"/>
</p>

jdDBusDebugger allows you to debug your D-Bus Interfaces with a easy to use GUI.Everything can be done from the GUI. No need to learn commandline tools.

jdDBusDebugger has macro support. It allows you to save all that you have done and repeat it to speed up your tests. You can also generate a shell script from your macros.

## Install

### Flatpak
You can get jdDBusDebugger from [Flathub](https://flathub.org/apps/details/page.codeberg.JakobDev.jdDBusDebugger)

### AUR
Arch Users can get jdDBusDebugger from the [AUR](https://aur.archlinux.org/packages/jddbusdebugger)

### pip
You can install jdDBusDebugger from [PyPI](https://pypi.org/project/jdDBusDebugger) using `pip`:
```shell
pip install jdDBusDebugger
```
Using this Method, it will not include a Desktop Entry or any other Data file, so you need to runjdDBusDebuggerfrom the Command Line.
Use this only, when nothing else works.

#### From source
This is only for experienced Users and someone, who wants to packagejdDBusDebuggerfor a Distro.
jdDBusDebugger should be installed as a Python package.
You can use `pip` or any other tool that can handle Python packages.
YOu need to have `lrelease` installed to build the Package.
After that, you should run `install-unix-datafiles.py` which wil install things like the Desktop Entry or the Icon in the correct place.
It defaults to `/usr`, but you can change it with the `--prefix` argument.
It also applies the translation to this files.
You need gettext installed to run `install-unix-datafiles.py`.

Here's a example of installingjdDBusDebuggerinto `/usr/local`:
```shell
sudo pip install --prefix /usr/local .
sudo ./install-unix-datafiles.py --prefix /usr/local
```

## Translate
You can help translating jdDBusDebugger on [Codeberg Translate](https://translate.codeberg.org/projects/jdDBusDebugger)

![Translation status](https://translate.codeberg.org/widget/jdDBusDebugger/jdDBusDebugger/multi-auto.svg)

## Develop
jdDBusDebugger is written in Python and uses PyQt6 as GUI toolkit. You should have some experience in both.
You can run `jdDBusDebugger.py`to startjdDBusDebuggerfrom source and test your local changes.
It ships with a few scripts in the tools directory that you need to develop.


#### CompileUI.py
This is the most important script. It will take all `.ui` files in `jdDBusDebugger/ui` and compiles it to a Python class
and stores it in `jdDBusDebugger/ui_compiled`. Without running this script first, you can't start jdDBusDebugger.
You need to rerun it every time you changed or added a `.ui` file.

#### BuildTranslations.py
This script takes all `.ts` files and compiles it to `.qm` files.
The `.ts` files are containing the translation source and are being used during the translation process.
The `.qm` contains the compiled translation and are being used by the Program.
You need to compile a `.ts` file to a `.qm` file to see the translations in the Program.

#### UpdateTranslations.py
This regenerates the `.ts` files. You need to run it, when you changed something in the source code.
The `.ts` files are contains the line in the source, where the string to translate appears,
so make sure you run it even when you don't changed a translatable string, so the location is correct.

####  UpdateUnixDataTranslations.py
This regenerates the translation files in `deploy/translations`. these files contains the translations for the Desktop Entry and the AppStream File.
It uses gettext, as it is hard to translate this using Qt.
These files just exists to integrate the translation with Weblate, because Weblate can't translate the Desktop Entry and the AppStream file.
Make sure you run this when you edited one of these files.
You need to have gettext installed to use it.