Protocol documentation

[Aleix Pol]

On Wed, Apr 19, 2017 at 9:27 PM, tastytea <kdeconnect at tastytea.de> wrote:
> On 2017-04-17 04:01 +0200
> Markus Slopianka <kamikazow at web.de> wrote:
>
>> On Freitag, 14. April 2017 22:03:20 CEST tastytea wrote:
>> > I want to use the daemon without KDE dependencies. It seems easier
>> > to reimplement than to remove the dependencies.
>>
>> There already is https://github.com/bboozzoo/mconnect – an
>> implementation of the protocol written using GLib only. It's an
>> inactive one-man project but it may serve as a starting point.
>
> Yes, I found that. Unfortunately it is written in a half-dead
> language (Vala).
>
>> There is also https://github.com/Bjoe/KConnectClientLib by a friend
>> of mine which is a proof of concept based on KDE Connect's upstream
>> code to run it on devices that don't ship anything but Qt itself. The
>> code was never properly cleaned up, so Qt-only building could be an
>> option at compile time and upstreamed. The code is three years old my
>> friend had to abandon his work because of time constrains.
>
> I didn't find that one, thanks. I'll look into it.
>
>> Considering that two people already tried to make a version free of
>> KDE Frameworks, better ask yourself if you really need that. Do you
>> need to run KDE Connect on some low-end embedded hardware or is it
>> just for PC users and some esoteric notion of "bloat"?
>
> I want to run it on low-end hardware and try to use as little ram as
> possible.

You can package it using Qt Lite:
http://blog.qt.io/blog/2016/08/18/introducing-the-qt-lite-project-qt-for-any-platform-any-thing-any-size/

Aleix