kdeconnect-kde

History

Aleix Pol c7cee37330 Port away from KServiceTrader Uses KPluginLoader+KPluginMetadata instead. Describes plugins in json instead of desktop files. These desktop files are then embedded into the .so file. All the plugins will be in a kdeconnect/ directory, and those will be the ones to look for. Note it doesn't drop the KService dependency as KIOCore is a KDE Connect dependency as well. REVIEW: 123042		2015-03-19 16:36:53 +01:00
..
batterydbusinterface.cpp	Remove kdebugnamespace completely and replace by core_debug	2014-09-22 00:59:34 +02:00
batterydbusinterface.h	Fixed notifications not being appearing in the model nor in the plasmoid	2014-07-01 01:26:07 +02:00
batteryplugin.cpp	Port away from KServiceTrader	2015-03-19 16:36:53 +01:00
batteryplugin.h	Port battery away from kDebug	2014-09-22 00:44:17 +02:00
CMakeLists.txt	Port away from KServiceTrader	2015-03-19 16:36:53 +01:00
kdeconnect_battery.json	Port away from KServiceTrader	2015-03-19 16:36:53 +01:00
README	Move the plugins into a different top-ĺevel directory	2014-06-14 16:34:11 +02:00

README

This plugins receives packages with type "kdeconnect.battery" and reads the
following fields:

isCharging (boolean): If the battery of the peer device is charging
currentCharge (int): The charge % of the peer device
thresholdEvent (int) [optional when = 0, see below]:
    means that a battery threshold event were fired on the remote device:
        0 := no event. generally not transmitted.
        1 := battery entered in low state
    This is an int so in the future we'll be able to subscribe to more events.
    (see BatteryPlugin.ThresholdBatteryEvent)

<TODO>
Symmetrically, it sends its own battery information in packages with the same
format.
</TODO>

It also sends packages with type kdeconnect.battery and a field "request": true,
to ask the peer device to send a package like the mentioned above, and should
also answer this same kind of packages with its own information.

If the battery is low and discharging, it will notify the user.