1. 03 Sep, 2020 1 commit
    • David Redondo's avatar
      Delete Clients in KsysGuardDaemon destructor · c47eb9ba
      David Redondo authored
      Clients and plugins are both children of the daemon. The Client destructor
      dereferences SensorProperties to unsubscribe from them. Because usually
      the object tree looks something like plugin -> sensorcontainer -> sensorobject -> sensorproperty
      we can not rely on the properties still being around when the clients are deleted.
      This fixes the segfault in the unit test detected by the address sanitizer.
      c47eb9ba
  2. 29 Jul, 2020 2 commits
  3. 09 Jun, 2020 1 commit
  4. 08 Jun, 2020 2 commits
  5. 19 May, 2020 4 commits
  6. 06 May, 2020 1 commit
    • David Edmundson's avatar
      Add a new daemon for stats monitoring · 75333fc1
      David Edmundson authored
      Summary:
      ksysguardd, whilst good, has a few problems
      
      The code is a bit archaic, it relies on a polling API, which is overhead
      for infrequently changed values or where setting up a monitor has a big
      overhead.
      
      It also moves the problem of translations into the daemon, allowing for
      better extensibility without requiring client side changes.
      
      The daemon is based around a typical OO model. Plugins have lists of
      objects, those objects have properties using common Qt patterns. A
      property also has various metadata.
      
      For full compatibility ksgrd is wrapped and the plan is to land with the
      bridge, then slowly land patches that use the new API natively.
      
      An nvidia plugin is also added to show the API being used in another
      format.
      
      This is all consumed by the new API posted in D28141
      
      Test Plan:
      Unit test
      Used with the new library to create a new suite of applet (upcoming patch)
      Used in a ported ksysguard
      
      Reviewers: #plasma, mart, ngraham, ahiemstra
      
      Reviewed By: #plasma, mart...
      75333fc1