Line 13: |
Line 13: |
| | | |
| ===Maliit=== | | ===Maliit=== |
− | [http://wiki.meego.com/Maliit Malit] You can run Maliit on Fedora 16: [https://wiki.maliit.org/Documentation/Installing#Fedora here are the installation guides for Fedora], latest available version is 0.91. On the XO this drags in 4,4 MB of QT and 12 MB of QT-X11. | + | [http://wiki.meego.com/Maliit Maliit] You can run Maliit on Fedora 16: [https://wiki.maliit.org/Documentation/Installing#Fedora here are the installation guides for Fedora], latest available version is 0.91. On the XO this drags in 4,4 MB of QT and 12 MB of QT-X11. |
| Put [http://download.opensuse.org/repositories/M17N:/Maliit/Fedora_16/M17N:Maliit.repo maliit.repo] in /etc/yum.repos.d/ | | Put [http://download.opensuse.org/repositories/M17N:/Maliit/Fedora_16/M17N:Maliit.repo maliit.repo] in /etc/yum.repos.d/ |
| yum install maliit-framework maliit-plugins | | yum install maliit-framework maliit-plugins |
Line 34: |
Line 34: |
| | | |
| Install the following rpms for build dependencies (as root): | | Install the following rpms for build dependencies (as root): |
− | yum install qt qt-x11 qt-devel libXcomposite-devel GConf2-devel gcc-c++ gcc make dbus-glib-devel dbus-devel gtk2-devel gtk3-devel git gtk-doc gobject-introspection-devel | + | yum install qt qt-x11 qt-devel libXcomposite-devel GConf2-devel gcc-c++ gcc make dbus-glib-devel dbus-devel gtk2-devel gtk3-devel git gtk-doc gobject-introspection-devel gdb doxygen |
| + | |
| + | If trying to build in the release candidate [http://wiki.laptop.org/go/Release_notes/12.1.0 os 14] you have to downgrade this packages: |
| + | yum downgrade libX11 libX11-common |
| | | |
| Get the sources: | | Get the sources: |
Line 42: |
Line 45: |
| Build the sources: | | Build the sources: |
| * First build the maliit-framework: | | * First build the maliit-framework: |
− | qmake-qt4 | + | git checkout 0.92.4 |
| + | qmake-qt4 CONFIG+=enable-dbus-activation |
| make | | make |
| sudo make install | | sudo make install |
| | | |
− | * Then build the maliit-plugins (you need to disable the sound-feedback here): | + | (If you build HEAD you can build with a [http://gitorious.org/maliit/maliit-framework/commit/6b9fc972d06b05a1c57749a1eec8b244b671d368 fix for the keyboard rotation], pass the DISABLE_TRANSLUCENT_BACKGROUND_HINT config) |
− | qmake-qt4 CONFIG+=disable-qt-mobility | + | |
| + | * Then build the maliit-plugins: |
| + | (you need HEAD here) |
| + | qmake-qt4 CONFIG+=MALIIT_DEFAULT_PROFILE=olpc-xo |
| make | | make |
| sudo make install | | sudo make install |
| | | |
− | * Update the IM_MODULES cache | + | * Update the IM_MODULES cache (as root) |
| gtk-query-immodules-3.0-32 > /usr/lib/gtk-3.0/3.0.0/immodules.cache | | gtk-query-immodules-3.0-32 > /usr/lib/gtk-3.0/3.0.0/immodules.cache |
− | gtk-query-immodules-2.0-32 > /usr/lib/gtk-2.0/2.10.0/gtk.immodules | + | <!-- gtk-query-immodules-2.0-32 > /usr/lib/gtk-2.0/2.10.0/gtk.immodules --> |
| | | |
| * Instruct GTK to use the Maliit IM_MODULE: | | * Instruct GTK to use the Maliit IM_MODULE: |
| Install the following [http://dev.laptop.org/~erikos/maliit/sugar-session sugar-session file] in /usr/bin/sugar-session. This sets the environment variable for 'GTK_IM_MODULE' to 'Maliit' on Sugar startup. | | Install the following [http://dev.laptop.org/~erikos/maliit/sugar-session sugar-session file] in /usr/bin/sugar-session. This sets the environment variable for 'GTK_IM_MODULE' to 'Maliit' on Sugar startup. |
| + | |
| + | * Change the style |
| + | To adjust your settings have a look at maliit-framework/examples/apps/maliit-exampleapp-settings-python3.py If you change the header to say '/usr/bin/python' to not try to use Python3 you can use it to do Maliit settings (you have to run the script from within Sugar). |
| + | |
| + | ./maliit-exampleapp-settings-python3.py about libmaliit-keyboard-plugin.so |
| + | ./maliit-exampleapp-settings-python3.py set libmaliit-keyboard-plugin.so current_style olpc-xo |
| + | |
| + | You can add as well several languages to be available: |
| + | |
| + | ./maliit-exampleapp-settings-python3.py set enabled libmaliit-keyboard-plugin.so:en_gb,libmaliit-keyboard-plugin.so:de |
| | | |
| ====Issues==== | | ====Issues==== |
Line 66: |
Line 83: |
| [http://www.gok.ca/ Gnome Onscreen Keyboard] | | [http://www.gok.ca/ Gnome Onscreen Keyboard] |
| | | |
− | ===Florenc=== | + | ===Florence=== |
− | [http://florence.sourceforge.net/english.html Florenc] | + | [http://florence.sourceforge.net/english.html Florence] |
| | | |
| ===Eekboard=== | | ===Eekboard=== |
Line 127: |
Line 144: |
| * Predictive text (context sensitive, locale sensitive) | | * Predictive text (context sensitive, locale sensitive) |
| * Square keys | | * Square keys |
| + | |
| + | ==Advancements== |
| + | |
| + | Keystrike accuracy will suffer compared to keys with tactile feedback. Users can compensate by visually aiming their keystrikes, but then spelling and textual context feedback will suffer because their eyes can't follow stdin and stdout or a transcription source and stdin at the same time. |
| + | |
| + | Once a keyboard layout has been determined, the home or neutral position of each hand—its 'center-of-mass'—can be recorded as a displacement from some keyboard reference coordinate. If there were software monitoring for drift in the 'center-of-mass' for either hand, the position of the on-screen keyboard could automatically drift in compensation (within limits) to preserve accuracy. |
| + | |
| + | Models of keyboarding styles would be needed to accommodate the many variations and patterns of keystroking in order to distinguish drift from 'in spec' intentional movement. Watch for research on this or other approaches to improve accuracy. --[[User:FGrose|FGrose]] 23:09, 22 August 2012 (EDT) |
| | | |
| ==Recommendation== | | ==Recommendation== |