Last indexation completed on 2024-12-29 05:28:19 UTC

 
  Name Size Date (UTC) Last indexed Description
  Name Size Date (UTC) Last indexed Description
folder Parent directory - 2024-02-11 01:50:27

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". 4. 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.json 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 findmyphoneplugin.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.


SEE ALSO: README.txt

file CMakeLists.txt 164 bytes 2024-02-11 01:50:27 -  
file kdeconnect_remotecommands.json 10042 bytes 2024-02-11 01:50:27 -  
file remotecommandsplugin.cpp 1845 bytes 2024-02-11 01:50:27 2024-12-29 04:34:27  
file remotecommandsplugin.h 1322 bytes 2024-02-11 01:50:27 2024-12-29 04:34:27