Subject: Input plans

From: Daniel van Vugt <[email-masked]>
Date: Wed, 02 Oct 2013 11:10:16 +0800

Do we have a roadmap for how to deal with the future of Mir input?

I mean, Mir uses Android input. When there's a bug or missing feature, 
do we intend to maintain and branch the Android input code? Is that more 
desirable than Mir having its own implementation to be molded as required?

- Daniel

---

From: Daniel d'Andrada <[email-masked]>
Date: Wed, 02 Oct 2013 05:06:35 -0300

On 02/10/13 00:10, Daniel van Vugt wrote:
> do we intend to maintain and branch the Android input code? Is that 
> more desirable than Mir having its own implementation to be molded as 
> required?
>

It's a fork of Android input code. Now it's pretty much intact (i.e. 
almost a verbatim copy of the original code) but the idea is that we 
will freely modify it to suite our needs (for better or worse). But once 
we start doing so we will also be taking in the burden of maintaining 
it. Which means covering it with tests etc. That's why I have been 
pushing some test-related patches for android-input code. Preparing the 
ground for upcoming modifications.