kdeconnect-kde

History

Aleix Pol a1a560c469 First approach to a KF5 port of KDE Connect Ported using KDELibs4Support, for a smaller delta, so we can keep developing on master until we decide not to. At the moment, it builds and installs but tests don't pass because of a QCA2 initialization problem I didn't manage to debug yet. CCMAIL: kdeconnect@kde.org		2014-06-16 20:02:07 +02:00
..
batterydbusinterface.cpp	Move the plugins into a different top-ĺevel directory	2014-06-14 16:34:11 +02:00
batterydbusinterface.h	Move the plugins into a different top-ĺevel directory	2014-06-14 16:34:11 +02:00
batteryplugin.cpp	First approach to a KF5 port of KDE Connect	2014-06-16 20:02:07 +02:00
batteryplugin.h	Move the plugins into a different top-ĺevel directory	2014-06-14 16:34:11 +02:00
CMakeLists.txt	First approach to a KF5 port of KDE Connect	2014-06-16 20:02:07 +02:00
kdeconnect_battery.desktop	Document in the desktop files the outgoing types for the plugins	2014-06-14 20:35:00 +02: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.