tristan/kdeconnect-kde
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix minor typos

Browse source
This commit is contained in:
Yuri Chornoivan 2019-12-22 10:15:58 +02:00
parent 01c4d0411b
commit ba8ee54558
6 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
README.md
View file

@ -17,7 +17,7 @@ All this is done completely wirelessly, utilising TLS encryption.
- Android, by installing the KDE Connect app from the [Play Store](https://play.google.com/store/apps/details?id=org.kde.kdeconnect_tp) or [F-Droid](https://f-droid.org/repository/browse/?fdid=org.kde.kdeconnect_tp). - Android, by installing the KDE Connect app from the [Play Store](https://play.google.com/store/apps/details?id=org.kde.kdeconnect_tp) or [F-Droid](https://f-droid.org/repository/browse/?fdid=org.kde.kdeconnect_tp).
## How to install ## 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](https://cgit.kde.org/kdeconnect-android.git/) These instructions explain how to install KDE Connect on your computer. You will also need to install it on your Android device and pair them together in the app before using this application. The Android app repository can be found [here](https://cgit.kde.org/kdeconnect-android.git/)
### On Linux ### 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](https://community.kde.org/KDEConnect#Building_KDE_Connect_.28Desktop.29) 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](https://community.kde.org/KDEConnect#Building_KDE_Connect_.28Desktop.29)
@ -47,11 +47,11 @@ The basic structure of a NetworkPacket is the following:
} }
``` ```
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. The content of the `"body"` section is defined by each Plugin. Hence, only the emitter 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: 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. `"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. `"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 ## Contributing

2
core/backends/bluetooth/connectionmultiplexer.cpp
View file

@ -29,7 +29,7 @@
#include "multiplexchannelstate.h" #include "multiplexchannelstate.h"
/** /**
* The default channel uuid. This channel is opened implicitely (without communication). * The default channel uuid. This channel is opened implicitly (without communication).
*/ */
#define DEFAULT_CHANNEL_UUID "a0d0aaf4-1072-4d81-aa35-902a954b1266" #define DEFAULT_CHANNEL_UUID "a0d0aaf4-1072-4d81-aa35-902a954b1266"

2
plugins/mousepad/waylandremoteinput.cpp
View file

@ -89,7 +89,7 @@ bool WaylandRemoteInput::handlePacket(const NetworkPacket& np)
//For drag'n drop //For drag'n drop
m_waylandInput->requestPointerButtonPress(Qt::LeftButton); m_waylandInput->requestPointerButtonPress(Qt::LeftButton);
} else if (isSingleRelease){ } else if (isSingleRelease){
//For drag'n drop. NEVER USED (release is done by tapping, which actually triggers a isSingleClick). Kept here for future-proofnes. //For drag'n drop. NEVER USED (release is done by tapping, which actually triggers a isSingleClick). Kept here for future-proofness.
m_waylandInput->requestPointerButtonRelease(Qt::LeftButton); m_waylandInput->requestPointerButtonRelease(Qt::LeftButton);
} else if (isScroll) { } else if (isScroll) {
m_waylandInput->requestPointerAxis(Qt::Vertical, dy); m_waylandInput->requestPointerAxis(Qt::Vertical, dy);

2
plugins/mousepad/x11remoteinput.cpp
View file

@ -149,7 +149,7 @@ bool X11RemoteInput::handlePacket(const NetworkPacket& np)
//For drag'n drop //For drag'n drop
XTestFakeButtonEvent(display, mainMouseButton, True, 0); XTestFakeButtonEvent(display, mainMouseButton, True, 0);
} else if (isSingleRelease){ } else if (isSingleRelease){
//For drag'n drop. NEVER USED (release is done by tapping, which actually triggers a isSingleClick). Kept here for future-proofnes. //For drag'n drop. NEVER USED (release is done by tapping, which actually triggers a isSingleClick). Kept here for future-proofness.
XTestFakeButtonEvent(display, mainMouseButton, False, 0); XTestFakeButtonEvent(display, mainMouseButton, False, 0);
} else if (isScroll) { } else if (isScroll) {
if (dy < 0) { if (dy < 0) {

2
plugins/sms/conversationsdbusinterface.h
View file

@ -117,7 +117,7 @@ Q_SIGNALS:
Q_SCRIPTABLE void conversationLoaded(qint64 conversationID, quint64 messageCount); Q_SCRIPTABLE void conversationLoaded(qint64 conversationID, quint64 messageCount);
private /*methods*/: private /*methods*/:
QString newId(); //Generates successive identifitiers to use as public ids QString newId(); //Generates successive identifiers to use as public ids
private /*attributes*/: private /*attributes*/:
const QString m_device; const QString m_device;

2
plugins/sms/smsplugin.h
View file

@ -48,7 +48,7 @@
* "body" : "Hello", // Text message body * "body" : "Hello", // Text message body
* "addresses": <List<Address>> // List of Address objects, one for each participant of the conversation * "addresses": <List<Address>> // List of Address objects, one for each participant of the conversation
* // The user's Address is excluded so: * // The user's Address is excluded so:
* // If this is a single-target messsage, there will only be one * // If this is a single-target message, there will only be one
* // Address (the other party) * // Address (the other party)
* // If this is an incoming multi-target message, the first Address is the * // If this is an incoming multi-target message, the first Address is the
* // sender and all other addresses are other parties to the conversation * // sender and all other addresses are other parties to the conversation