9f34092aa9
The HIG recommend that buttons with an action label that require further user input end in an ellipsis, and that dialog buttons should clearly indicate what they do. Button labels typically do not match the given exceptions that license sentence case. Currently, the main "Add command" button in the configuration button does not end in an ellipsis even though it opens a dialog, is sentence case, and the dialog has a "Save" rather than the customary "Add" that is used for these kinds of actions, in particular in kcms. The dialog title is also not translatable. This change adds the ellipsis, converts the button to title case, makes the dialog title translatable, and adds an "Add" button as an action to the dialog. |
||
---|---|---|
.. | ||
battery | ||
bigscreen | ||
clipboard | ||
connectivity-report | ||
contacts | ||
findmyphone | ||
findthisdevice | ||
lockdevice | ||
mmtelephony | ||
mousepad | ||
mpriscontrol | ||
mprisremote | ||
notifications | ||
pausemusic | ||
ping | ||
presenter | ||
remotecommands | ||
remotecontrol | ||
remotekeyboard | ||
remotesystemvolume | ||
runcommand | ||
screensaver-inhibit | ||
sendnotifications | ||
sftp | ||
share | ||
sms | ||
systemvolume | ||
telephony | ||
virtualmonitor | ||
CMakeLists.txt | ||
kdeconnect.notifyrc | ||
kdeconnect.schema.json | ||
Messages.sh | ||
README.txt |
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. 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). 3. 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. Now you have an empty skeleton to implement your new plugin logic.