Skip to content
Alexander Akulich edited this page Feb 26, 2019 · 2 revisions

Telepathy Debugger

The plan is to develop libTpDebuggerQt — a backend for Telepathy debug messages monitor based on spec. The lib can base on KTp Debugger

What is wrong with KTp Debugger?

  • It does not detect services "on the fly"
  • It shows only connected CMs
  • It hardcodes mission control
  • It shows the same service as many times, as the service registered on the bus
  • It doesn't have QML UI
  • It mixes logic and widget
  • It looks like a part of KTp, but actually it does not depend on KTp

Subtasks

  1. Extract logic from the (widget-based) UI
  2. Reimplement service detection, so the debugger would be able to monitor all processes with exposed Debug interface
  3. Implement a widget-based GUI for desktop
  4. Reimplement KTp Debugger on top of the new classes
  5. Add a message model for QML
  6. Implement a QQC2-based UI for mobile devices
  7. Implement a Silica-based UI for Sailfish OS

Frontends

  • Pure Qt
  • KTP Debugger (ported to this lib)
  • QML-based debugger for Plasma Mobile
  • QML-based debugger for Sailfish OS

C++/Qt-based replacement for DBus debugger (Bustle)

What is Bustle

https://blogs.gnome.org/wjjt/2008/11/13/bustle-a-d-bus-activity-charting-tool/

https://willthompson.co.uk/bustle/0.4.0-video.webm

QDBusMonitor (the replacement project)

Repository: qdbusmonitor

Status: initial development