Ive been wanting this integration for years and was thinking with Wayland support in both KDE and Input Leap, the wish is finally ripe. I have another post looking for a mentor to help me implement what Id like to do here get some help mapping out what needs to be done. I’m not sure where to start or what individual tasks need to be done. What am I overlooking/unaware of? Other thoughts and insights?
Input Leap
I have been using the Input Leap fork. It works quite well (once connected), seems to have a tight scope and transparent management. Integrating with Input Leap rather than implementing the synergy protocol appears the way to go. The general goals would be to use KDE Connect to improve UX .
UI
- Show discovered devices on a layout
- Identify which discovered device is to be server or which keyboard/mouse to share.
- Drag & drop discovered screens into the desired layout
- Few options to configure
- Several options the Input Leap UI exposes would be taken care of by KDE Connect. Emphasis on auto-config, users wanting to manually do something can do it outside of KDE Connect.
Coordination
- Use kde connect to discover all devices that are Input Leap enabled
- I dont think Input Leap can be controlled over d-bus but it does use d-bus for some events. Input Leap a cli and non-daemon mode, use KDE Connect to send the options needed to run the command?
- Which synced clipboard, probably KDE Connects?
Deeper Integration
- Encryption: Utilize KDE Connect’s existing end-to-end encryption for all Input Leap traffic?
- Authentication: Leverage KDE Connect’s pairing mechanism instead of Input Leaps?
- Network Restrictions: Implement KDE Connect’s trusted networks feature to limit Input Leap connections to specific WiFi networks?
- Wake up devices on screen edge>