1. 23 Jan, 2017 1 commit
  2. 19 Jan, 2017 1 commit
  3. 14 Jan, 2017 1 commit
  4. 13 Jan, 2017 5 commits
  5. 11 Jan, 2017 4 commits
  6. 10 Jan, 2017 2 commits
    • 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
    • Aleix Pol Gonzalez's avatar
      Reduce API exposed through dbus · 3734d6ce
      Aleix Pol Gonzalez authored
      Don't use QDBusConnection::ExportAllContents
      No need to make connect and receivedPackage public slots (they're are the
      parent's already)
      Fixes T4975
      Test Plan: Rough manual test
      Reviewers: #kde_connect, albertvaka
      Reviewed By: #kde_connect, albertvaka
      Maniphest Tasks: T4975
      Differential Revision: https://phabricator.kde.org/D3871
  7. 06 Jan, 2017 2 commits
  8. 05 Jan, 2017 1 commit
  9. 04 Jan, 2017 1 commit
  10. 01 Jan, 2017 2 commits
  11. 22 Dec, 2016 1 commit
  12. 20 Dec, 2016 2 commits
  13. 17 Dec, 2016 1 commit
  14. 14 Dec, 2016 1 commit
  15. 02 Dec, 2016 1 commit
  16. 30 Nov, 2016 3 commits
  17. 28 Nov, 2016 4 commits
  18. 26 Nov, 2016 7 commits