64062b3cc9
Summary: Drop support for creating notifications from the SMS plugin. The old usecase is better handled by the notifications plugin reply box anyway Rename packets defined in SMS plugin from PACKET_TYPE_TELEPHONY_* to PACKET_TYPE_SMS_* Update TELEPHONY plugin packet description to point to SMS plugin Define TELEPHONY_REQUEST_MUTE packet to replace old TELEPHONY_REQUEST with mute event field Please see Android-side patch here: D15544 Test Plan: I see four test cases, based on the version of the app being used, where "old" means any version built with sources not containing this revision and "new" means any version built with sources using this revision: - New Android vs. New Desktop - Supported and works for me - New Android vs. Old Desktop - Supported and works for me - Old Android vs. New Desktop - Not supported - Download a new app from the Play store or F-Droid - Old Android vs. Old Desktop - If this is broken, it is not my fault :) In the supported use cases: - Test SMS reply - Receive SMS (or MMS!) message - Verify that the //notification// plugin forwards a replyable notification and that replying works - Test incoming call ringer mute - Enable ringer volume (not vibrate) - Receive phone call - Verify a desktop notification with a Mute button appears - Verify that clicking the mute button causes the phone to stop making the ringer noise (vibration not affected) Reviewers: #kde_connect, albertvaka, nicolasfella Reviewed By: #kde_connect, albertvaka, nicolasfella Subscribers: nicolasfella, kdeconnect Tags: #kde_connect Differential Revision: https://phabricator.kde.org/D15543 |
||
|---|---|---|
| app | ||
| cli | ||
| cmake | ||
| core | ||
| daemon | ||
| declarativeplugin | ||
| doc | ||
| icon | ||
| indicator | ||
| interfaces | ||
| kcm | ||
| kcmplugin | ||
| kio | ||
| nautilus-extension | ||
| plasmoid | ||
| plugins | ||
| sfos | ||
| smsapp | ||
| tests | ||
| urlhandler | ||
| .arcconfig | ||
| .arclint | ||
| .gitignore | ||
| CMakeLists.txt | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| kdeconnect-version.h.in | ||
| KDEConnectMacros.cmake | ||
| org.kde.kdeconnect.kcm.appdata.xml | ||
| 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.
- 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.
All this without wires, over the already existing WiFi network, and using TLS encryption.
Supported platforms
- Computers running Linux with Plasma 5, Gnome 3, Elementary OS...
- Android, by installing the KDE Connect Android app (also available on F-Droid).
How to install
This explains how to install KDE Connect on your computer. You will also need to install it in your phone and pair both devices in the app if you want it to be any useful.
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 :)
If you are not using Plasma 5, you might want to install a user interface for your platform. The indicator-kdeconnect project provides an appindicator icon plus integration with Nautilus.
On Mac or Windows
Platforms other than Linux are not officially supported, but it should be possible to run KDE Connect there. You can compile KDE Connect for Windows using Craft and it works except for some plugins. I haven't tried on Mac. Contributions 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.
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.