Actually, this isn't just an Xmir issue. It could be needed for any non-Qt app running on Touch.
Normally it's just the app's toolkit that sets this up so it would not seem like Xmir needs to get involved. But there might be some level of Xmir involvement in the conversation between the X app and the shell.
On the other hand, we could just add one OSK button (to rule them all) that Xmir and other non-integrated toollkits could benefit from.
As a third option - Could we make Unity8 just provide an OSK show/hide button/panel in the case that it detects a non-integrated app?
It's worth noting still that the backend-frontend design of input methods means that Xmir probably won't be involved in this enhancement. Just the backend that your Gnome-app-in-Xmir uses talks to the frontend that is the Unity8 OSK.
Actually, this isn't just an Xmir issue. It could be needed for any non-Qt app running on Touch.
Normally it's just the app's toolkit that sets this up so it would not seem like Xmir needs to get involved. But there might be some level of Xmir involvement in the conversation between the X app and the shell.
On the other hand, we could just add one OSK button (to rule them all) that Xmir and other non-integrated toollkits could benefit from.
As a third option - Could we make Unity8 just provide an OSK show/hide button/panel in the case that it detects a non-integrated app?
It's worth noting still that the backend-frontend design of input methods means that Xmir probably won't be involved in this enhancement. Just the backend that your Gnome-app-in-Xmir uses talks to the frontend that is the Unity8 OSK.