kdeconnect-kde/plugins
Aniket Kumar f211d7e401 Add feature to start new conversation with existing contacts
## Summary

Start a conversation with contacts having no previous conversation with.

It is currently only possible to use the messaging app to send a message to a conversation which already exists.

This patch implements this feature by integrating all contacts having no prior conversation with the recent conversations in the recent conversation list and at the bottom in a sorted manner, something like this,

The contacts are stored in the recent conversation list model as a conversation but with INVALID conversation ID and INVALID conversation DATE.

## Testing

Testing just needs kdeconnect daemon to be recompiled and executed.
2020-03-21 22:57:28 +00:00
..
battery SVN_SILENT made messages (.desktop file) - always resolve ours 2019-08-07 05:00:07 +02:00
clipboard SVN_SILENT made messages (.desktop file) - always resolve ours 2019-08-07 05:00:07 +02:00
contacts SVN_SILENT made messages (.desktop file) - always resolve ours 2019-12-19 05:49:03 +01:00
findmyphone SVN_SILENT made messages (.desktop file) - always resolve ours 2020-03-21 09:48:57 +01:00
findthisdevice SVN_SILENT made messages (.desktop file) - always resolve ours 2020-03-17 10:05:04 +01:00
lockdevice Rename DbusHelper => DBusHelper 2019-08-14 17:36:19 +02:00
mousepad Fix minor typos 2019-12-22 10:15:58 +02:00
mpriscontrol Merge branch 'strace/kdeconnect-kde-seamless_playback' 2020-03-21 00:24:49 +01:00
mprisremote Adds an MPRIS server for controlling other device's MPRIS services 2020-03-15 23:46:56 +01:00
notifications Fix minor EBN issues 2019-12-22 09:49:55 +02:00
pausemusic SVN_SILENT made messages (.desktop file) - always resolve ours 2020-03-17 10:05:04 +01:00
photo SVN_SILENT made messages (.desktop file) - always resolve ours 2019-12-25 05:45:20 +01:00
ping SVN_SILENT made messages (.desktop file) - always resolve ours 2019-09-29 05:09:20 +02:00
presenter SVN_SILENT made messages (.desktop file) - always resolve ours 2020-02-14 05:56:20 +01:00
remotecommands SVN_SILENT made messages (.desktop file) - always resolve ours 2019-12-19 05:49:03 +01:00
remotecontrol SVN_SILENT made messages (.desktop file) - always resolve ours 2019-12-19 05:49:03 +01:00
remotekeyboard SVN_SILENT made messages (.desktop file) - always resolve ours 2020-03-21 09:48:57 +01:00
remotesystemvolume Make plugins work in SailfishConnect 2020-03-01 20:00:40 +00:00
runcommand Use kdeconnect-settings for command configuration 2020-03-21 21:26:51 +01:00
screensaver-inhibit SVN_SILENT made messages (.desktop file) - always resolve ours 2020-03-11 06:07:22 +01:00
sendnotifications SVN_SILENT made messages (.desktop file) - always resolve ours 2020-03-17 10:05:04 +01:00
sftp Fix minor EBN issues 2019-12-22 09:49:55 +02:00
share SVN_SILENT made messages (.desktop file) - always resolve ours 2020-03-17 10:05:04 +01:00
sms Add feature to start new conversation with existing contacts 2020-03-21 22:57:28 +00:00
systemvolume SVN_SILENT made messages (.desktop file) - always resolve ours 2019-12-25 05:45:20 +01:00
telephony Make incoming call notification persistent 2020-03-15 23:34:52 +02:00
CMakeLists.txt Make plugins work in SailfishConnect 2020-03-01 20:00:40 +00:00
kdeconnect.notifyrc SVN_SILENT made messages (.desktop file) - always resolve ours 2020-03-17 10:05:04 +01:00
kdeconnect_plugin.desktop SVN_SILENT made messages (.desktop file) - always resolve ours 2020-03-17 10:05:04 +01:00
Messages.sh Figure out Messages.sh after code refactoring 2014-06-17 18:45:47 +02:00
README.txt Fix typos 2018-07-27 15:00:23 +02:00

Writing a plugin for KDE Connect
=================================

For the desktop client (this project):
--------------------------------------

1. Enter the "plugins" directory.
2. Copy the "ping" under a different name ("findmyphone" in this example).
3. Add "add_subdirectory(findmyphone)" to CMakeLists.txt after the others "add_subdirectory".
1. Enter the new "findmyphone" directory.
5. Edit CMakeLists.txt by replacing "ping" with "findmyphone".
6. Rename other files in this directory by replacing "ping" with "findmyphone"
7. Write a description of your plugin into "README"
8. Edit findmyphoneplugin.cpp and findmyphoneplugin.h.
  A. Change license header.
  B. Replace (case sensitive) "ping" with "findmyphone", "PingPlugin" with "FindMyPhonePlugin" and "PING" with "FINDMYPHONE".
9. Edit kdeconnect_findmyphone.desktop file:
  A. Replace "ping" with "findmyphone".
  B. Change name, description, icon, author, email, version, website, license info.
  C. Remove all the translations
  D. Set X-KDEConnect-SupportedPacketType and X-KDEConnect-OutgoingPacketType to the packet type your plugin will receive
     and send, respectively. In this example this is "kdeconnect.findmyphone". Make sure that this matches what is defined in
     the findmyplugin.h file (in the line "#define PACKET_TYPE_..."), and also in Android.
10. Now you have an empty skeleton to implement your new plugin logic.

For Android (project kdeconnect-android):
-----------------------------------------

1. Change directory to src/org/kde/kdeconnect/Plugins.
2. Copy "PingPlugin" under a different name ("FindMyPhonePlugin" in this example).
1. Enter the new "FindMyPhonePlugin" directory.
4. Rename "PingPlugin.java" to "FindMyPhonePlugin.java"
5. Edit it. Replace (case sensitive) "Ping" with "FindMyPhone", "ping" with "findmyphone", "PING" with "FINDMYPHONE"
   and "plugin_ping" with "plugin_findmyphone".
6. Open res/values/strings.xml. Find and copy the lines "pref_plugin_ping_desc" and "pref_plugin_ping" replacing "ping"
   with "findmyphone" and edit the plugin name and description between <string> </string>).
7. Open src/org/kde/kdeconnect/Plugins/PluginFactory.java.
  A. Copy "import … PingPlugin" line with replacing "PingPlugin" with "FindMyPhonePlugin".
  B. Copy "PluginFactory.registerPlugin(PingPlugin.class);" line with replacing "PingPlugin" with "FindMyPhonePlugin".
8. Open src/org/kde/kdeconnect/NetworkPacket.java. Copy a "public final static String PACKET_TYPE_PING = …" line
   replacing "PING" with the packet type you will be using (should match the desktop client).
9. Now you have an empty skeleton to implement your new plugin logic.