Package: jdDBusDebugger
jdDBusDebuggerAn advanced D-Bus DebuggerjdDBusDebugger 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.InstallFlatpakYou can get jdDBusDebugger fromFlathubAURArch Users can get jdDBusDebugger from theAURpipYou can install jdDBusDebugger fromPyPIusingpip:pipinstalljdDBusDebuggerUsing 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 sourceThis is only for experienced Users and someone, who wants to packagejdDBusDebuggerfor a Distro.
jdDBusDebugger should be installed as a Python package.
You can usepipor any other tool that can handle Python packages.
YOu need to havelreleaseinstalled to build the Package.
After that, you should runinstall-unix-datafiles.pywhich 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--prefixargument.
It also applies the translation to this files.
You need gettext installed to runinstall-unix-datafiles.py.Here's a example of installingjdDBusDebuggerinto/usr/local:sudopipinstall--prefix/usr/local.
sudo./install-unix-datafiles.py--prefix/usr/localTranslateYou can help translatingjdDBusDebuggeronCodeberg TranslateDevelopjdDBusDebugger is written in Python and uses PyQt6 as GUI toolkit. You should have some experience in both.
You can runjdDBusDebugger.pyto startjdDBusDebuggerfrom source and test your local changes.
It ships with a few scripts in the tools directory that you need to develop.CompileUI.pyThis is the most important script. It will take all.uifiles injdDBusDebugger/uiand compiles it to a Python class
and stores it injdDBusDebugger/ui_compiled. Without running this script first, you can't start jdDBusDebugger.
You need to rerun it every time you changed or added a.uifile.BuildTranslations.pyThis script takes all.tsfiles and compiles it to.qmfiles.
The.tsfiles are containing the translation source and are being used during the translation process.
The.qmcontains the compiled translation and are being used by the Program.
You need to compile a.tsfile to a.qmfile to see the translations in the Program.UpdateTranslations.pyThis regenerates the.tsfiles. You need to run it, when you changed something in the source code.
The.tsfiles 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.pyThis regenerates the translation files indeploy/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.