desktop-packages team mailing list archive
Mailing list archive
[Bug 1543351] Re: Add on-screen-keyboard support for Xmir/Puritine apps
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.
** Changed in: xorg-server (Ubuntu)
Status: Triaged => Incomplete
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
Add on-screen-keyboard support for Xmir/Puritine apps
Status in Canonical Pocket Desktop:
Status in Ubuntu UX:
Status in unity8 package in Ubuntu:
Status in xorg-server package in Ubuntu:
From perspective of product management - this is currently not a
requirement, just want to capture it for future
we currently can't interact with puritine apps relying on the OSK
to add this feature in where text-box selection on an xapp results in
triggering the osk, in unity8 would be a very large/complicated
effort. However, with a manual capability to trigger the OSK this
could be achieved.
For design team
one idea was to add a show/hide button for the OSK.
realizing this may be undesirable to add another indicator item - a follow-on idea might be to add an alpha button in the corner of the xmir-root window (the window that holds any xapp at the moment)
this way the button presence would only be limited to the Xapp interaction.
To manage notifications about this bug go to: