e77c1c87ac
Summary: As mentioned on telegram, there are some fundamental issues with bluetooth. The only approach I could get working was multiplexing: manually sending multiple streams of data over a single connection. This is the description of that multiplexing protocol. I have an implementation of this protocol, but I'd first like some feedback to see if this is what we're going to use before finishing up those patches. See the document itself for more details. I make the protocol forward-compatible, although I don't expect we will need ever that. Test Plan: None, this is just a description. Reviewers: #kde_connect, andyholmes, albertvaka Reviewed By: #kde_connect, albertvaka Subscribers: albertvaka, kdeconnect Tags: #kde_connect Differential Revision: https://phabricator.kde.org/D17987 |
||
|---|---|---|
| app | ||
| cli | ||
| cmake | ||
| core | ||
| daemon | ||
| data | ||
| declarativeplugin | ||
| doc | ||
| icon | ||
| indicator | ||
| interfaces | ||
| kcm | ||
| kcmplugin | ||
| kio | ||
| nautilus-extension | ||
| plasmoid | ||
| plugins | ||
| sfos | ||
| smsapp | ||
| tests | ||
| urlhandler | ||
| .arcconfig | ||
| .arclint | ||
| .editorconfig | ||
| .gitignore | ||
| CMakeLists.txt | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| kdeconnect-version.h.in | ||
| KDEConnectMacros.cmake | ||
| README.md | ||
KDE Connect - desktop app
KDE Connect is a multi-platform app that allows your devices to communicate (eg: your phone and your computer).
(Some) Features
- Shared clipboard: copy and paste between your phone and your computer (or any other device).
- Notification sync: Read and reply to your Android notifications from the desktop.
- Share files and URLs instantly from one device to another including some filesystem integration.
- Multimedia remote control: Use your phone as a remote for Linux media players.
- Virtual touchpad: Use your phone screen as your computer's touchpad and keyboard.
- Presentation remote: Advance your presentation slides straight from your phone.
All this is done completely wirelessly, utilising TLS encryption.
Supported platforms
- Computers running Linux with Plasma 5, Gnome 3, Elementary OS... any distro with Qt5 support given a little work :)
- Android, by installing the KDE Connect app from the Play Store or F-Droid.
How to install
These instructions explain how to install KDE Connect on your computer. You will also need to install it on your Andriod device and pair them together in the app before using this application. The Android app repository can be found here
On Linux
Look in your distribution repo for a package called kdeconnect-kde, kdeconnect-plasma, or just kdeconnect. If it's not there and you know how to build software from sources, you just found the repo :), instructions are here
On Mac or Windows
Platforms other than Linux are not officially supported, as there has yet to be an official release of KDE Connect for MacOS or Windows. However, most of the features have already been ported to windows so you can compile KDE Connect for Windows using Craft. It hasn't yet been completely tested on MacOS, contributions and feedback are welcome!
On BSD
It should work, but no promises :)
How does it work?
KDE Connect consists of an UI-agnostic "core" library which exposes a series of DBus interfaces, and several UI components that consume these DBus interfaces. This way, new UI components can be added to integrate better with specific platforms or desktops, without having to reimplement the protocol or any of the internals. The core KDE Connect library is also divided in 4 big blocks:
- LinkProviders: Are in charge of discovering other KDE Connect-enabled devices in the network and establishing a Link to them.
- Devices: Represent a remote device, abstracting the specific Link that is being used to reach it.
- NetworkPackets: JSON-serializable and self-contained pieces of information to be sent by the plugins between devices.
- Plugins: Independent pieces of code which implement a specific feature. Plugins will use NetworkPackets to exchange information through the network with other Plugins on a remote Device.
The basic structure of a NetworkPacket is the following:
{
"id": 123456789,
"type": "com.example.myplugin",
"body": { },
"version": 5
}
The content of the "body" section is defined by each Plugin. Hence, only the emisor and receiver plugins of a given packet type need agree on the contents of the body.
NetworkPackets can also have binary data attached that can't be serialized to JSON. In this case, two new fields will be added:
"payloadSize": The size of the file, or -1 if it is a stream without known size.
"payloadTransferInfo": Another JSON object where the specific Link can add information so the Link in the remote end can establish a connection and receive the payload (eg: IP and port in a local network). It's up to the Link implementation to decide how to use this field.
Contributing
To contribute patches, use KDE Connect's Phabricator. There you can also find a task list with stuff to do, and links to other relevant resources. It is a good idea to also subscribe to the KDE Connect mailing list. We can also be reached on IRC at #kdeconnect on freenode or on telegram, contributions and feedback are warmly welcomed.
License
GNU GPL v2 and GNU GPL v3
If you are reading this from Github, you should know that this is just a mirror of the KDE Project repo.