kdeconnect-kde

History

Àlex Fiestas dbea3171bd Make kdeconnect core compile without KDELibs4Support This meant to add a lot of dependencies to each plugin since we had KDELibs4support as PUBLIC link meaning that anything linking against kdeconnectcore was linking at the same time to mostly all frameworks. Now each plugin has more or less its dependencies in the CMake some still depend on KDELibs4Support. For the mousepad plugin I needed to add a fixX11.h file that basically undefines/defines again some stuff xlib has that conflcits with normal C++ and Qt. Before it was not conflicting because some lib within KDELibs4Support was including this file, but now we have to do it ourselves.		2014-09-22 02:40:51 +02: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	Make kdeconnect core compile without KDELibs4Support	2014-09-22 02:40:51 +02:00
batteryplugin.h	Port battery away from kDebug	2014-09-22 00:44:17 +02:00
CMakeLists.txt	Make kdeconnect core compile without KDELibs4Support	2014-09-22 02:40:51 +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.