Hi, > Am 25.04.2016 um 22:10 schrieb Xavi Drudis Ferran <xdru...@tinet.cat>: > > El Mon, Apr 25, 2016 at 09:46:21PM +0200, Josua Mayer deia: >> It appears to me that QtMoko was using the inputmethod functionality >> provided by QT and just implemented the onscreen keyboard on top. Check the >> code for it below: >> https://github.com/radekp/qtmoko/tree/master/src/plugins/inputmethods/fingerkeyboard >> >> So the current abstraction is InputMethod. And that should be operative no >> matter which window-system QT was built for. > > Yes, but I'm a bit lost. Didn't you want something you could use without Qt ? > Or I misunderstood ? I'm not sure I know what the goal is now.
I think we are still discussing the goal :) The overall goal of QtMoko.net is to get a new and modernized QtMoko. A subgoal is to have a good touch keyboard. Depending on whether we simply make QtMoko build again (a) or port/rewrite it to be based on Qt5 libraries (b) we either can use the existing touch keyboard code or have to find something new (for b). > > In fact I think QWSInputMethod is specific to Qt-Embedded in particular. > I think (but haven't looked) it is not in Qt for X11, for example. > > http://doc.qt.io/qt-4.8/qwsinputmethod.html Yes, that is QtE only. And "A Qt for Embedded Linux application requires a server application to be running, or to be the server application itself. All system generated events, including keyboard and mouse events, are passed to the server application which then propagates the event to the appropriate client." > > I mean when you said: > > El Mon, Apr 25, 2016 at 11:54:19AM +0200, H. Nikolaus Schaller deia: >> >> But I have no idea if the on-screen keyboard can be rewritten in a >> way that it works with all other GUI applications (not necessarily Qt >> based!). You would get a problem if you have network-manager and >> can't type IP addresses... So this might be a big challenge (who >> doesn't love challenges?). > > I thought you mean to take the logic in the qtmoko keyboard and > change the inputmethod for some other more widely available keyboard > abstraction. The problem is that there is no really widely available abstraction. The most common denominator are the input events of the kernel. All GUI libraries (Qt, GTK, wxWidgets, Xlib etc.) provide their own. This is not a problem for standard applications that use an existing system keyboard, like a desktop / notebook. The problem I see arises if we want to present context dependent keyboard layouts like it is done on other mobile OS. This would mean that an application can send information to the keyboard process. BTW: I have pushed a very simple Qt5 "hello world" application that can be easily built on and runs on a GTA04: http://git.goldelico.com/?p=gta04-qtmoko.git;a=commit;h=e480c6a059e95af52feda75f07a35302a7ff448a BR, Nikolaus _______________________________________________ Community mailing list Community@openphoenux.org http://lists.goldelico.com/mailman/listinfo.cgi/community http://www.openphoenux.org
