Hey, I’m working on input methods on Wayland thanks to NLNet support and I’d like to use iced as a showcase for protocol improvements
- because Rust makes it easy
- because iced looks cool
but currently, iced doesn’t quite support the full functionality of text-input. For example, it doesn’t send the surrounding text to the input method and it doesn’t support notifying the user of the kind of stuff that’s in the text field. Right now it’s because winit doesn’t have it, so it’d be easy to fix. Would that be welcome?
With this done, the Wayland protocol is still flawed. For example, it’s not clear how to move the cursor without a keyboard, how to move to the next input, setting persistent text-input IDs, likely more. I’d like to build protocol drafts and submit them to wayland-protocols along with proofs of concept in iced - private branches if necessary, but it only makes sense if you are ready at some point when it’s nearly ready to accept the new protocol upstream.
Could you imagine supporting the development of the protocol? If not by merging submitted-but-not-yet-ratified protocol changes, then would some other way be better?