Unsolved keyboard for android and ios using Qt
-
Hi, does anyone know how to implement a keyboard (input method) for android, and ios(optional) using qml?
Simple example would be great. -
@seniorivn
QtVirtualKeyboard
The plugin basics have to be done in C++. What you then show (QML panel) is up to you. -
The Qt Virtual Keyboard project provides an input framework and reference keyboard frontend for Qt 5 on Linux Desktop/X11, Windows Desktop, and Boot2Qt targets.
No any mention about android or ios. Are you sure it's the right direction to look?
-
Hi and welcome to devnet,
Why do you need a virtual keyboard for these OSs ? Input like TextLine should trigger the native keyboard.
-
@seniorivn said in keyboard for android and ios using qml:
No any mention about android or ios. Are you sure it's the right direction to look?
oops, my fault, sry
-
@SGaist that's the point, i want to develop a keyboard that will be shown up as native
-
So a keyboard application like SwiftKey ?
-
@SGaist yes, exactly(but very different ui, that i'm able to develop)
-
Just to be sure I understand correctly, you want to do a custom keyboard for other applications to use ? Or just for your own application ?
-
@SGaist yes, i want to create custom keyboard using qt library, for other applications to use on android and ios(hopefully).
P.S. oh, god, i'm feeling like the worst english speaker ever.
-
Don't worry you're not, but since both cases can be valid, it's best to ensure that we are talking about the same thing. Up until recently there was no way to write custom keyboard for iOS.
From a quick look at the related documentation on iOS, you may have to customize things a bit yourself in order to have a keyboard application using Qt.
-
@SGaist well, at least keyboard for android, i was hoping to find an example here, but i found it by myself https://github.com/synasius/qt-custom-keyboard-proof
i will try to make it work(for now i can't)
And i've created an issue on bug tracker about support for android and ios by qtvirtualkeyboard https://bugreports.qt.io/browse/QTBUG-56983