1. 18 Jul, 2020 1 commit
  2. 21 Feb, 2020 1 commit
    • George Vogiatzis's avatar
      [Plasmoid]Make device menu use PC ContextMenu · 875cf16a
      George Vogiatzis authored
      Summary:
      Change the three dotted menu to use PlasmaComponents ContextMenu.
      This prevents menu from staying open on other system tray's applets.
      Wayland still has that issue, happens in other menus too.
      BUG: 415142
      
      And change menu icon into a hamburger menu.
      
      Test Plan:
      Before:
      Open the menu, and then open an other applet. Menu will stay open on
      the left. Even if change windows and open the system tray, will still
      be there.
      After:
      Use X11. By clicking, for example volume applet, menu will minimize.
      Will need to click again to open the applet.
      875cf16a
  3. 12 Oct, 2019 2 commits
  4. 15 Aug, 2019 1 commit
  5. 21 Jul, 2019 1 commit
  6. 25 Jun, 2019 1 commit
  7. 15 Jun, 2019 3 commits
  8. 23 Mar, 2019 1 commit
  9. 31 Jan, 2019 1 commit
  10. 02 Jan, 2019 1 commit
    • Simon Redman's avatar
      Implement Drag n Drop file transfer on the plasmoid · bafbc344
      Simon Redman authored
      Summary:
      A DropArea has been added to the ListItem representing a device in the
      plasmoid based on what is done in the Quickshare plasmoid. This enables
      Drag n Drop of files onto a section of the plasmoid to transfer files.
      
      The DropArea has the size of the ListItem which is a rectangle
      including the title of the device down to the button to share text.
      Additionally, there is a tooltip area covering the DropArea to indicate
      that it is possible to drop a file to send it to the device. Multiple files
      can be sent at once.
      
      Ref T8288
      
      Test Plan: Drag and Drop one or many files onto the widget, the files should be transferred to the connected device.
      
      Reviewers: #kde_connect, sredman
      
      Reviewed By: #kde_connect, sredman
      
      Subscribers: sredman, kdeconnect
      
      Tags: #kde_connect
      
      Maniphest Tasks: T8288
      
      Differential Revision: https://phabricator.kde.org/D17611
      bafbc344
  11. 26 Nov, 2018 1 commit
  12. 22 Nov, 2018 1 commit
  13. 09 Nov, 2018 1 commit
  14. 08 Nov, 2018 1 commit
    • Nicolas Fella's avatar
      Share RemoteKeyboard implementation · 952da637
      Nicolas Fella authored
      Summary: Extract RemoteKeyboard.qml into declarativeplugin to be able to use it from both plasmoid and app without code duplication
      
      Reviewers: #kde_connect, hkaelberer, apol
      
      Reviewed By: #kde_connect, apol
      
      Subscribers: kdeconnect, mtijink, apol, #kde_connect
      
      Tags: #kde_connect
      
      Differential Revision: https://phabricator.kde.org/D12670
      952da637
  15. 07 Nov, 2018 1 commit
  16. 02 Nov, 2018 3 commits
  17. 01 Nov, 2018 1 commit
  18. 30 Oct, 2018 1 commit
  19. 04 Oct, 2018 1 commit
  20. 06 Sep, 2018 1 commit
  21. 27 Jul, 2018 1 commit
  22. 14 Jun, 2018 1 commit
  23. 08 May, 2018 1 commit
    • Nicolas Fella's avatar
      Start cleaning up RemoteKeyboard QML code · 4d8863ba
      Nicolas Fella authored
      Summary:
      The code for visually disabling the input field is not needed any more since the field is completely hidden when not needed. Also drop the custom available property from the text field.
      
      More cleanups will follow. My long-term goal is to reuse the code in the app to enable remote keyboard input on non-Plasma DEs
      
      Test Plan: (De)activate the remote keyboard on Android.
      
      Reviewers: #kde_connect, apol
      
      Reviewed By: #kde_connect, apol
      
      Subscribers: apol, #kde_connect
      
      Tags: #kde_connect
      
      Differential Revision: https://phabricator.kde.org/D12669
      4d8863ba
  24. 24 Mar, 2018 1 commit
  25. 22 Aug, 2017 1 commit
  26. 01 Aug, 2017 1 commit
    • Nicolas Fella's avatar
      Gave plasmoid some love · 3c3b5b03
      Nicolas Fella authored
      Summary:
      Make the plasmoid content transparent
      Include battery info in header
      Only show remotekeyboard input if available
      Make header always centered
      
      before:
      {F3820966}
      
      after:
      {F3820965}
      
      Reviewers: #kde_connect, apol
      
      Reviewed By: #kde_connect, apol
      
      Subscribers: jeanv, albertvaka, apol, #kde_connect
      
      Tags: #kde_connect
      
      Differential Revision: https://phabricator.kde.org/D6943
      3c3b5b03
  27. 27 Jul, 2017 1 commit
    • Nicolas Fella's avatar
      Gave plasmoid some love · 66e5eefe
      Nicolas Fella authored
      Summary:
      Make the plasmoid content transparent
      Include battery info in header
      Only show remotekeyboard input if available
      Make header always centered
      
      before:
      {F3820966}
      
      after:
      {F3820965}
      
      Reviewers: #kde_connect, apol
      
      Reviewed By: #kde_connect, apol
      
      Subscribers: jeanv, albertvaka, apol, #kde_connect
      
      Tags: #kde_connect
      
      Differential Revision: https://phabricator.kde.org/D6943
      66e5eefe
  28. 12 Jul, 2017 1 commit
    • Fabian Vogt's avatar
      Treat device names as plaintext, not rich text · 5641d818
      Fabian Vogt authored
      Summary:
      Notifications, QML Text and QLabel accept a HTML subset,
      which does not make sense for device names.
      
      BUG: 382243
      
      Test Plan:
      Sent a pair request and accepted it, device name
      now shown as plain text everywhere.
      
      Reviewers: #kde_connect, albertvaka
      
      Reviewed By: #kde_connect, albertvaka
      
      Subscribers: #kde_connect
      
      Differential Revision: https://phabricator.kde.org/D6640
      5641d818
  29. 01 Jun, 2017 1 commit
    • Julian Wolff's avatar
      show icon and reply toolbutton in plasmoid · 8aaa1884
      Julian Wolff authored
      Summary:
      Show an icon for each notification which has an icon.
      
      	Show a toolbutton which can be used to reply to notifications which offer a quick reply.
      
      Reviewers: #kde_connect, albertvaka
      
      Reviewed By: #kde_connect, albertvaka
      
      Subscribers: albertvaka
      
      Maniphest Tasks: T4674, T4658
      
      Differential Revision: https://phabricator.kde.org/D6058
      8aaa1884
  30. 23 Jan, 2017 1 commit
  31. 11 Jan, 2017 1 commit
  32. 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
      040ad735
  33. 03 Oct, 2016 1 commit
  34. 06 Sep, 2016 1 commit
  35. 21 Aug, 2016 1 commit