Since the headless-keyboard seems to be a central component of the app, it would be helpful for the overall user experience to integration the keyboard layout more into the Qt app.
At the moment, both the Qt app must be started (, the server must be running) and the alternative keyboard layout must be selected until the app is ready to be used in headless mode.
The keyboard layout should be capable of launch everthing so that the user only needs to switch to the alternative keyboard layout in order to use the app in headless mode.
Limitations
The solution should be implemented the sailfish way so that it passes harbour store validation. However, since the headless-keyboard layout is not distributed in harbour and downloaded by the user, that does not count for the keyboard layout :grinning:
TODO
[ ] Provide new methods and signals in the dbus service of the headless-keyboard layout to start the Qt app and to start / stop the server
[ ] Fire sailfish UI notifications whenever the server is started so the user is informed even though the Qt app is not active
Since the headless-keyboard seems to be a central component of the app, it would be helpful for the overall user experience to integration the keyboard layout more into the Qt app.
At the moment, both the Qt app must be started (, the server must be running) and the alternative keyboard layout must be selected until the app is ready to be used in headless mode.
The keyboard layout should be capable of launch everthing so that the user only needs to switch to the alternative keyboard layout in order to use the app in headless mode.
Limitations The solution should be implemented the sailfish way so that it passes harbour store validation. However, since the headless-keyboard layout is not distributed in harbour and downloaded by the user, that does not count for the keyboard layout :grinning:
TODO
Useful resources
Community Please comment this issue :+1: if you think this feature may be any useful or if something is missing :wink: