1. 12 Jun, 2019 6 commits
  2. 09 Jun, 2019 1 commit
  3. 30 Apr, 2019 1 commit
  4. 24 Mar, 2019 1 commit
  5. 13 Mar, 2019 1 commit
  6. 07 Nov, 2018 1 commit
    • Nicolas Fella's avatar
      [app] Add system volume control · 2f76d214
      Nicolas Fella authored
      Summary: Add a remote systemvolume plugin.
      Test Plan:
      Change volume via slider -> Volume on target changes
      Change volume on target -> Slider changes
      Mute via button -> Mute on target changes
      Mute on target -> Button changes icon
      Add/remove sink on host -> Sink is add/removed in list
      Reviewers: #kde_connect, apol
      Reviewed By: #kde_connect, apol
      Subscribers: apol, kdeconnect
      Tags: #kde_connect
      Differential Revision: https://phabricator.kde.org/D16667
  7. 31 Oct, 2018 1 commit
  8. 10 Sep, 2018 1 commit
    • Simon Redman's avatar
      Split SMS and Telephony plugin on desktop · bcc9fb06
      Simon Redman authored
      Telephony and SMS handling are quite distinct so they should be in separate plugins for better maintainability, given that @sredman has big plans with SMS.
      This diff should be fully backwards compatible, but whether we really want to do that is up to discussion
      Test Plan: Only supeficially tested. Receive an SMS (old way), Notification is shown
      Reviewers: #kde_connect, sredman
      Reviewed By: sredman
      Subscribers: albertvaka, apol, sredman, kdeconnect, #kde_connect
      Tags: #kde_connect
      Differential Revision: https://phabricator.kde.org/D13594
  9. 20 Jun, 2018 1 commit
    • Nicolas Fella's avatar
      Enable running commands from app · 17e1e1ec
      Nicolas Fella authored
      The RemotecommandsPlugin lacks a graphical frontend.
      Inlcudes a Dbus Interface for fetching the commands and a Model exposing them to QML. For this I oriented on the NotificatonsPlugin.
      Test Plan:
      Open command list in app, check available commands, trigger some. Do same for CLI.
      Activate edit action, check KCM opening on remote device, add command, check for new command in list
      Reviewers: #kde_connect, apol
      Reviewed By: #kde_connect, apol
      Subscribers: apol, kdeconnect, #kde_connect
      Tags: #kde_connect
      Differential Revision: https://phabricator.kde.org/D13503
  10. 09 Jun, 2018 1 commit
    • Aleix Pol Gonzalez's avatar
      (WIP) Upgrade Telephony plugin to read SMS history (KDE side) · 31e93ef7
      Aleix Pol Gonzalez authored
      For real usecases of SMS support, we will almost always need access to the message history in some way
      Specifically resolve T8338
      Incidentally resolve T6651 since Telephony shall no longer create a notification
      Test Plan:
      - Build corresponding Android-side diff (D11698)
      - Build this diff
      Step 1: Does anything at all work?
      - Put a breakpoint in the handleBatchMessages method of the telephony plugin, ideally after constructing a Message object
      - Use DBus to poke /modules/kdeconnect/devices/<deviceID>/telephony.requestAllConversations()
      - Verify that the constructed Message is one you sent or received and that it is the most recent in the corresponding conversation
      Step 2: DBus
      - Open the Interface org.kde.kdeconnect.device.conversations of /modules/kdeconnect/devices/<deviceId>
      - Poke activeConversations and verify an empty array is returned
      - Poke requestAllConversationThreads
      - Poke activeConversations and verify that a list of numbers has been returned. These are conversationIds
      - Use a conversationId to call getFirstFromConversation
        - Verify that the returned Message object is one which you recognize
        - Note that if the message is an MMS it will be blank and meaningless. Try a different conversationId. MMS support "coming soon!"
      Step 3: SMS App
      - Use ccmake (or similar) to set SMSAPP_ENABLE to ON
      - Build the project
      - Run ./bin/kdeconnect-sms
      - Verify that the app shows a list of everyone you have an SMS conversation with (MMS messages are stripped out)
        - If you have the Contacts plugin working, verify that most contacts have their name and photo instead of their phone number
      Reviewers: #kde_connect, nicolasfella, apol
      Reviewed By: #kde_connect, nicolasfella, apol
      Subscribers: andyholmes, apol, nicolasfella, #kde_connect
      Tags: #kde_connect
      Maniphest Tasks: T8338, T6651
      Differential Revision: https://phabricator.kde.org/D11854
  11. 25 Mar, 2018 1 commit
    • Aleix Pol Gonzalez's avatar
      Optionally include sms app · c863feef
      Aleix Pol Gonzalez authored
      Creates a tiny messaging app that uses KPeople to query the contacts and
      KDE connect telephony plugins to send plugins.
      To be ready, still needs some work on the contacts sync side and some
      messages history would be nice.
  12. 23 Jan, 2017 1 commit
  13. 11 Jan, 2017 1 commit
  14. 10 Jan, 2017 1 commit
    • Holger Kaelberer's avatar
      kdeconnect-kde: Add remotekeyboard plugin · 040ad735
      Holger Kaelberer authored
      Allow to inject keypress events to remote peers (most notably Android devices)
      Notes / open issues / possible improvements:
      - For the json-payload I used the syntax of the key-events as sent by mousepad-plugin with the addition of a "sendAck"-flag. If "sendAck" is set to true the remote peer should echo a key-event if it could be handled, thus allowing the local client to find out whether the key was accepted. For performance reasons, it's allowed to send multi-char strings in the "key" property (performs much better if you send a whole string via "echo '...' |  kdeconnect-cli ..." e.g.)
      - kdeconnect-cli: For now takes a string and transforms it into single key-events for visible characters only. In a first implementation I used a kbhit() helper that used termios.h to catch and relay keypresses interactively (including some special-events), which was not optimal. A better approch might be to use linux input-api directly. Would this be an option regarding cross-platform compatibility or can I assume to develop for Linux only? Being a command-line guy, I'd really like to have a fully featured kdeconnect-cli interface ;-)
      - Factor out the Qt::Key-to-internal keymap to some core-helper because it corresponds to the mapping in the mousepad-plugin?
      - The plasmoid is not perfect as it is: A single line containing a non-echoing TextField (i.e. it eats all the KeyPress events), and only ack-ed keypress-packets from the peer device are injected if they contain visible keys. Advantage: the user sees whether his key-presses are accepted by the peer device. Disadvantage: The echoed text does not correspond 1:1 to what is shown on the peer's display, user might be confused when typing without success. I played around with different variations each of which with its proper shortcomings:
      1. An echoing Textfield for typing: Has the advantage that the user can directly see what he is typing, which makes interaction in the typing field easier, BUT messes up interaction if the Editor on the peer is changed silently and does not notify the user if his keypresses are not handled by the peer.
      2. A non-echoing TextField for typing PLUS a readonly one for printing visible echoed keys. Disadvantage: same as for the previous one and uses more space on the plasmoid.
      Comments? Ideas?
      REVIEW: 129727
      BUG: 370919
  15. 15 Jun, 2016 1 commit
  16. 12 Jun, 2016 1 commit
  17. 12 Sep, 2015 2 commits
  18. 11 Sep, 2015 1 commit
    • David Edmundson's avatar
      Find my phone plugin · 9985a596
      David Edmundson authored
      Add a plugin that sends a package to ring an alarm on a phone
      Also adjusts plasmoid to have a button to invoke this.
  19. 22 Jul, 2015 3 commits
  20. 18 Jun, 2015 2 commits
  21. 11 Jun, 2015 1 commit
  22. 18 May, 2015 1 commit
  23. 19 Mar, 2015 1 commit
    • Aleix Pol Gonzalez's avatar
      Port away from KServiceTrader · c7cee373
      Aleix Pol Gonzalez authored
      Uses KPluginLoader+KPluginMetadata instead.
      Describes plugins in json instead of desktop files. These desktop files are
      then embedded into the .so file. All the plugins will be in a kdeconnect/
      directory, and those will be the ones to look for.
      Note it doesn't drop the KService dependency as KIOCore is a KDE Connect
      dependency as well.
      REVIEW: 123042
  24. 12 Mar, 2015 1 commit
  25. 09 Mar, 2015 1 commit
  26. 24 Feb, 2015 1 commit
  27. 05 Feb, 2015 1 commit
  28. 21 Sep, 2014 1 commit
  29. 12 Sep, 2014 1 commit
  30. 01 Jul, 2014 1 commit
  31. 30 Jun, 2014 1 commit