kdeconnect-kde/plugins/contacts/contactsplugin.h

163 lines
5.6 KiB
C
Raw Normal View History

Add contacts-reading plugin (KDE side) Summary: Add a plugin to KDE Connect which supports exporting the Android contacts databases to vcards on the desktop When the devices are connected, the plugin sends a request for all timestamps and IDs When a packet with timestamps and IDs is received, it verifies it has vcards for each ID and that the timestamps match and deletes any vcards for IDs which were not reported. It then sends a request for all vcards which were missing or need updating When a packet with vcards is received they are unconditionally written to disk, possibly overwriting existing vcards Provides one dbus method: contacts/synchronizeRemoteWithLocal which triggers the request for all timestamps and IDs BUG: 367999 Test Plan: Connect the device to the desktop and verify that vcards are created in QStandardPaths::GenericDataLocation / kpeoplevcard". On my system this is ~/.local/share/kpeoplevcard Create a dummy contact on the device and verify it is synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Modify the dummy contact and verify the modifications are synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Delete the dummy contact and verify the deletion is synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Reviewers: #kde_connect, apol Reviewed By: #kde_connect, apol Subscribers: mtijink, #kde_connect, apol Tags: #kde_connect Maniphest Tasks: T8283 Differential Revision: https://phabricator.kde.org/D9691
2018-04-23 21:27:38 +01:00
/**
* Copyright 2018 Simon Redman <simon@ergotech.com>
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License as
* published by the Free Software Foundation; either version 2 of
* the License or (at your option) version 3 or any later version
* accepted by the membership of KDE e.V. (or its successor approved
* by the membership of KDE e.V.), which shall act as a proxy
* defined in Section 14 of version 3 of the license.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
2019-03-23 16:29:26 +00:00
* along with this program. If not, see <https://www.gnu.org/licenses/>.
Add contacts-reading plugin (KDE side) Summary: Add a plugin to KDE Connect which supports exporting the Android contacts databases to vcards on the desktop When the devices are connected, the plugin sends a request for all timestamps and IDs When a packet with timestamps and IDs is received, it verifies it has vcards for each ID and that the timestamps match and deletes any vcards for IDs which were not reported. It then sends a request for all vcards which were missing or need updating When a packet with vcards is received they are unconditionally written to disk, possibly overwriting existing vcards Provides one dbus method: contacts/synchronizeRemoteWithLocal which triggers the request for all timestamps and IDs BUG: 367999 Test Plan: Connect the device to the desktop and verify that vcards are created in QStandardPaths::GenericDataLocation / kpeoplevcard". On my system this is ~/.local/share/kpeoplevcard Create a dummy contact on the device and verify it is synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Modify the dummy contact and verify the modifications are synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Delete the dummy contact and verify the deletion is synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Reviewers: #kde_connect, apol Reviewed By: #kde_connect, apol Subscribers: mtijink, #kde_connect, apol Tags: #kde_connect Maniphest Tasks: T8283 Differential Revision: https://phabricator.kde.org/D9691
2018-04-23 21:27:38 +01:00
*/
#ifndef CONTACTSPLUGIN_H
#define CONTACTSPLUGIN_H
class QObject;
Add contacts-reading plugin (KDE side) Summary: Add a plugin to KDE Connect which supports exporting the Android contacts databases to vcards on the desktop When the devices are connected, the plugin sends a request for all timestamps and IDs When a packet with timestamps and IDs is received, it verifies it has vcards for each ID and that the timestamps match and deletes any vcards for IDs which were not reported. It then sends a request for all vcards which were missing or need updating When a packet with vcards is received they are unconditionally written to disk, possibly overwriting existing vcards Provides one dbus method: contacts/synchronizeRemoteWithLocal which triggers the request for all timestamps and IDs BUG: 367999 Test Plan: Connect the device to the desktop and verify that vcards are created in QStandardPaths::GenericDataLocation / kpeoplevcard". On my system this is ~/.local/share/kpeoplevcard Create a dummy contact on the device and verify it is synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Modify the dummy contact and verify the modifications are synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Delete the dummy contact and verify the deletion is synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Reviewers: #kde_connect, apol Reviewed By: #kde_connect, apol Subscribers: mtijink, #kde_connect, apol Tags: #kde_connect Maniphest Tasks: T8283 Differential Revision: https://phabricator.kde.org/D9691
2018-04-23 21:27:38 +01:00
#include <QStandardPaths>
#include <core/kdeconnectplugin.h>
/**
* Used to request the device send the unique ID and last-changed timestamp of every contact
*/
#define PACKET_TYPE_CONTACTS_REQUEST_ALL_UIDS_TIMESTAMP QStringLiteral("kdeconnect.contacts.request_all_uids_timestamps")
/**
* Used to request the vcards for the contacts corresponding to a list of UIDs
*
* It shall contain the key "uids", which will have a list of uIDs (long int, as string)
*/
#define PACKET_TYPE_CONTACTS_REQUEST_VCARDS_BY_UIDS QStringLiteral("kdeconnect.contacts.request_vcards_by_uid")
/**
* Response indicating the package contains a list of all contact uIDs and last-changed timestamps
*
* It shall contain the key "uids", which will mark a list of uIDs (long int, as string)
* then, for each UID, there shall be a field with the key of that UID and the value of the timestamp (int, as string)
*
* For example:
* ( 'uids' : ['1', '3', '15'],
* '1' : '973486597',
* '3' : '973485443',
* '15' : '973492390' )
*
* The returned IDs can be used in future requests for more information about the contact
*/
#define PACKAGE_TYPE_CONTACTS_RESPONSE_UIDS_TIMESTAMPS QStringLiteral("kdeconnect.contacts.response_uids_timestamps")
/**
* Response indicating the package contains a list of contact vcards
*
* It shall contain the key "uids", which will mark a list of uIDs (long int, as string)
* then, for each UID, there shall be a field with the key of that UID and the value of the remote's vcard for that contact
*
* For example:
* ( 'uids' : ['1', '3', '15'],
* '1' : 'BEGIN:VCARD\n....\nEND:VCARD',
* '3' : 'BEGIN:VCARD\n....\nEND:VCARD',
* '15' : 'BEGIN:VCARD\n....\nEND:VCARD' )
*/
#define PACKET_TYPE_CONTACTS_RESPONSE_VCARDS QStringLiteral("kdeconnect.contacts.response_vcards")
/**
* Where the synchronizer will write vcards and other metadata
* TODO: Per-device folders since each device *will* have different uIDs
*/
Q_GLOBAL_STATIC_WITH_ARGS(
QString, vcardsLocation,
(QStandardPaths::writableLocation(QStandardPaths::GenericDataLocation) + ("/kpeoplevcard")))
#define VCARD_EXTENSION QStringLiteral(".vcf")
#define METADATA_EXTENSION QStringLiteral(".meta")
typedef QString uID;
Q_DECLARE_METATYPE(uID)
typedef QStringList uIDList_t;
Q_DECLARE_METATYPE(uIDList_t)
class Q_DECL_EXPORT ContactsPlugin : public KdeConnectPlugin {
Q_OBJECT
Q_CLASSINFO("D-Bus Interface", "org.kde.kdeconnect.device.contacts")
public:
2019-05-04 15:15:49 +01:00
explicit ContactsPlugin(QObject* parent, const QVariantList& args);
Add contacts-reading plugin (KDE side) Summary: Add a plugin to KDE Connect which supports exporting the Android contacts databases to vcards on the desktop When the devices are connected, the plugin sends a request for all timestamps and IDs When a packet with timestamps and IDs is received, it verifies it has vcards for each ID and that the timestamps match and deletes any vcards for IDs which were not reported. It then sends a request for all vcards which were missing or need updating When a packet with vcards is received they are unconditionally written to disk, possibly overwriting existing vcards Provides one dbus method: contacts/synchronizeRemoteWithLocal which triggers the request for all timestamps and IDs BUG: 367999 Test Plan: Connect the device to the desktop and verify that vcards are created in QStandardPaths::GenericDataLocation / kpeoplevcard". On my system this is ~/.local/share/kpeoplevcard Create a dummy contact on the device and verify it is synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Modify the dummy contact and verify the modifications are synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Delete the dummy contact and verify the deletion is synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Reviewers: #kde_connect, apol Reviewed By: #kde_connect, apol Subscribers: mtijink, #kde_connect, apol Tags: #kde_connect Maniphest Tasks: T8283 Differential Revision: https://phabricator.kde.org/D9691
2018-04-23 21:27:38 +01:00
~ContactsPlugin () override;
2019-05-04 15:15:49 +01:00
bool receivePacket(const NetworkPacket& np) override;
void connected() override {
Add contacts-reading plugin (KDE side) Summary: Add a plugin to KDE Connect which supports exporting the Android contacts databases to vcards on the desktop When the devices are connected, the plugin sends a request for all timestamps and IDs When a packet with timestamps and IDs is received, it verifies it has vcards for each ID and that the timestamps match and deletes any vcards for IDs which were not reported. It then sends a request for all vcards which were missing or need updating When a packet with vcards is received they are unconditionally written to disk, possibly overwriting existing vcards Provides one dbus method: contacts/synchronizeRemoteWithLocal which triggers the request for all timestamps and IDs BUG: 367999 Test Plan: Connect the device to the desktop and verify that vcards are created in QStandardPaths::GenericDataLocation / kpeoplevcard". On my system this is ~/.local/share/kpeoplevcard Create a dummy contact on the device and verify it is synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Modify the dummy contact and verify the modifications are synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Delete the dummy contact and verify the deletion is synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Reviewers: #kde_connect, apol Reviewed By: #kde_connect, apol Subscribers: mtijink, #kde_connect, apol Tags: #kde_connect Maniphest Tasks: T8283 Differential Revision: https://phabricator.kde.org/D9691
2018-04-23 21:27:38 +01:00
}
QString dbusPath () const override;
protected:
/**
* Path where this instance of the plugin stores its synchronized contacts
*/
QString vcardsPath;
public Q_SLOTS:
/**
* Query the remote device for all its uIDs and last-changed timestamps, then:
* Delete any contacts which are known locally but not reported by the remote
* Update any contacts which are known locally but have an older timestamp
* Add any contacts which are not known locally but are reported by the remote
*/
2019-05-04 15:15:49 +01:00
Q_SCRIPTABLE void synchronizeRemoteWithLocal();
Add contacts-reading plugin (KDE side) Summary: Add a plugin to KDE Connect which supports exporting the Android contacts databases to vcards on the desktop When the devices are connected, the plugin sends a request for all timestamps and IDs When a packet with timestamps and IDs is received, it verifies it has vcards for each ID and that the timestamps match and deletes any vcards for IDs which were not reported. It then sends a request for all vcards which were missing or need updating When a packet with vcards is received they are unconditionally written to disk, possibly overwriting existing vcards Provides one dbus method: contacts/synchronizeRemoteWithLocal which triggers the request for all timestamps and IDs BUG: 367999 Test Plan: Connect the device to the desktop and verify that vcards are created in QStandardPaths::GenericDataLocation / kpeoplevcard". On my system this is ~/.local/share/kpeoplevcard Create a dummy contact on the device and verify it is synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Modify the dummy contact and verify the modifications are synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Delete the dummy contact and verify the deletion is synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Reviewers: #kde_connect, apol Reviewed By: #kde_connect, apol Subscribers: mtijink, #kde_connect, apol Tags: #kde_connect Maniphest Tasks: T8283 Differential Revision: https://phabricator.kde.org/D9691
2018-04-23 21:27:38 +01:00
public:
Q_SIGNALS:
/**
* Emitted to indicate that we have locally cached all remote contacts
*
* @param newContacts The list of just-synchronized contacts
*/
2019-05-04 15:15:49 +01:00
Q_SCRIPTABLE void localCacheSynchronized(const uIDList_t& newContacts);
Add contacts-reading plugin (KDE side) Summary: Add a plugin to KDE Connect which supports exporting the Android contacts databases to vcards on the desktop When the devices are connected, the plugin sends a request for all timestamps and IDs When a packet with timestamps and IDs is received, it verifies it has vcards for each ID and that the timestamps match and deletes any vcards for IDs which were not reported. It then sends a request for all vcards which were missing or need updating When a packet with vcards is received they are unconditionally written to disk, possibly overwriting existing vcards Provides one dbus method: contacts/synchronizeRemoteWithLocal which triggers the request for all timestamps and IDs BUG: 367999 Test Plan: Connect the device to the desktop and verify that vcards are created in QStandardPaths::GenericDataLocation / kpeoplevcard". On my system this is ~/.local/share/kpeoplevcard Create a dummy contact on the device and verify it is synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Modify the dummy contact and verify the modifications are synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Delete the dummy contact and verify the deletion is synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Reviewers: #kde_connect, apol Reviewed By: #kde_connect, apol Subscribers: mtijink, #kde_connect, apol Tags: #kde_connect Maniphest Tasks: T8283 Differential Revision: https://phabricator.kde.org/D9691
2018-04-23 21:27:38 +01:00
protected:
/**
* Handle a packet of type PACKAGE_TYPE_CONTACTS_RESPONSE_UIDS_TIMESTAMPS
*
* For every uID in the reply:
* Delete any from local storage if it does not appear in the reply
* Compare the modified timestamp for each in the reply and update any which should have changed
* Request the details any IDs which were not locally cached
*/
2019-05-04 15:15:49 +01:00
bool handleResponseUIDsTimestamps(const NetworkPacket&);
Add contacts-reading plugin (KDE side) Summary: Add a plugin to KDE Connect which supports exporting the Android contacts databases to vcards on the desktop When the devices are connected, the plugin sends a request for all timestamps and IDs When a packet with timestamps and IDs is received, it verifies it has vcards for each ID and that the timestamps match and deletes any vcards for IDs which were not reported. It then sends a request for all vcards which were missing or need updating When a packet with vcards is received they are unconditionally written to disk, possibly overwriting existing vcards Provides one dbus method: contacts/synchronizeRemoteWithLocal which triggers the request for all timestamps and IDs BUG: 367999 Test Plan: Connect the device to the desktop and verify that vcards are created in QStandardPaths::GenericDataLocation / kpeoplevcard". On my system this is ~/.local/share/kpeoplevcard Create a dummy contact on the device and verify it is synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Modify the dummy contact and verify the modifications are synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Delete the dummy contact and verify the deletion is synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Reviewers: #kde_connect, apol Reviewed By: #kde_connect, apol Subscribers: mtijink, #kde_connect, apol Tags: #kde_connect Maniphest Tasks: T8283 Differential Revision: https://phabricator.kde.org/D9691
2018-04-23 21:27:38 +01:00
/**
* Handle a packet of type PACKET_TYPE_CONTACTS_RESPONSE_VCARDS
*/
2019-05-04 15:15:49 +01:00
bool handleResponseVCards(const NetworkPacket&);
Add contacts-reading plugin (KDE side) Summary: Add a plugin to KDE Connect which supports exporting the Android contacts databases to vcards on the desktop When the devices are connected, the plugin sends a request for all timestamps and IDs When a packet with timestamps and IDs is received, it verifies it has vcards for each ID and that the timestamps match and deletes any vcards for IDs which were not reported. It then sends a request for all vcards which were missing or need updating When a packet with vcards is received they are unconditionally written to disk, possibly overwriting existing vcards Provides one dbus method: contacts/synchronizeRemoteWithLocal which triggers the request for all timestamps and IDs BUG: 367999 Test Plan: Connect the device to the desktop and verify that vcards are created in QStandardPaths::GenericDataLocation / kpeoplevcard". On my system this is ~/.local/share/kpeoplevcard Create a dummy contact on the device and verify it is synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Modify the dummy contact and verify the modifications are synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Delete the dummy contact and verify the deletion is synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Reviewers: #kde_connect, apol Reviewed By: #kde_connect, apol Subscribers: mtijink, #kde_connect, apol Tags: #kde_connect Maniphest Tasks: T8283 Differential Revision: https://phabricator.kde.org/D9691
2018-04-23 21:27:38 +01:00
/**
* Send a request-type packet which contains no body
*
* @return True if the send was successful, false otherwise
*/
2019-05-04 15:15:49 +01:00
bool sendRequest(const QString& packetType);
Add contacts-reading plugin (KDE side) Summary: Add a plugin to KDE Connect which supports exporting the Android contacts databases to vcards on the desktop When the devices are connected, the plugin sends a request for all timestamps and IDs When a packet with timestamps and IDs is received, it verifies it has vcards for each ID and that the timestamps match and deletes any vcards for IDs which were not reported. It then sends a request for all vcards which were missing or need updating When a packet with vcards is received they are unconditionally written to disk, possibly overwriting existing vcards Provides one dbus method: contacts/synchronizeRemoteWithLocal which triggers the request for all timestamps and IDs BUG: 367999 Test Plan: Connect the device to the desktop and verify that vcards are created in QStandardPaths::GenericDataLocation / kpeoplevcard". On my system this is ~/.local/share/kpeoplevcard Create a dummy contact on the device and verify it is synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Modify the dummy contact and verify the modifications are synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Delete the dummy contact and verify the deletion is synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Reviewers: #kde_connect, apol Reviewed By: #kde_connect, apol Subscribers: mtijink, #kde_connect, apol Tags: #kde_connect Maniphest Tasks: T8283 Differential Revision: https://phabricator.kde.org/D9691
2018-04-23 21:27:38 +01:00
/**
* Send a request-type packet which has a body with the key 'uids' and the value the list of
* specified uIDs
*
* @param packageType Type of package to send
* @param uIDs List of uIDs to request
* @return True if the send was successful, false otherwise
*/
2019-05-04 15:15:49 +01:00
bool sendRequestWithIDs(const QString& packetType, const uIDList_t& uIDs);
Add contacts-reading plugin (KDE side) Summary: Add a plugin to KDE Connect which supports exporting the Android contacts databases to vcards on the desktop When the devices are connected, the plugin sends a request for all timestamps and IDs When a packet with timestamps and IDs is received, it verifies it has vcards for each ID and that the timestamps match and deletes any vcards for IDs which were not reported. It then sends a request for all vcards which were missing or need updating When a packet with vcards is received they are unconditionally written to disk, possibly overwriting existing vcards Provides one dbus method: contacts/synchronizeRemoteWithLocal which triggers the request for all timestamps and IDs BUG: 367999 Test Plan: Connect the device to the desktop and verify that vcards are created in QStandardPaths::GenericDataLocation / kpeoplevcard". On my system this is ~/.local/share/kpeoplevcard Create a dummy contact on the device and verify it is synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Modify the dummy contact and verify the modifications are synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Delete the dummy contact and verify the deletion is synchronized (Currently not automatic, have to disconnect and reconnect or use dbus) Reviewers: #kde_connect, apol Reviewed By: #kde_connect, apol Subscribers: mtijink, #kde_connect, apol Tags: #kde_connect Maniphest Tasks: T8283 Differential Revision: https://phabricator.kde.org/D9691
2018-04-23 21:27:38 +01:00
};
#endif // CONTACTSPLUGIN_H