[Bug 43722] New: High level bindings for o.f.T.Debug

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=43722

             Bug #: 43722
           Summary: High level bindings for o.f.T.Debug
    Classification: Unclassified
           Product: Telepathy
           Version: git master
          Platform: Other
               URL: http://cgit.collabora.com/git/user/gkiagia/telepathy-q
                    t4.git/log/?h=debug-receiver
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: tp-qt4
        AssignedTo: telepathy-bugs at lists.freedesktop.org
        ReportedBy: kiagiadakis.george at gmail.com
         QAContact: telepathy-bugs at lists.freedesktop.org


Hi,

I started playing a bit with the o.f.T.Debug interface, wanting to implement a
log viewer for tp-kde. So, I added low level generated bindings and a high
level class called "DebugReceiver" (to match the TpDebugSender of tp-glib,
which is the server-side), together with the helper "PendingDebugMessageList"
to carry the return value of the "GetMessages" method.

The implementation is far from perfect, but I submit it here for discussion. I
think the spec is problematic because there is no way of tracking the "Enabled"
property (so you cannot reliably cache it) and also there is no
reference-counting on "Enabled", so if I set it to false in my program, any
other possible log viewer that is running at that time will malfunction. I went
for the option of not exporting "Enabled" at all to the user and use a Feature
instead to enable it. The problem with this is that I cannot set it back to
false later, so all the services will continue to have the overhead of emitting
debug messages on the bus after my log viewer closes. Ideas welcome.

Branch at:
http://cgit.collabora.com/git/user/gkiagia/telepathy-qt4.git/log/?h=debug-receiver

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.
You are the assignee for the bug.