3,267
edits
Changes
Jump to navigation
Jump to search
Line 13:
Line 13: − + − No you can run the 'maliit-keyboard-viewer' example.+ − + + + − + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + − + − + Line 39:
Line 93: + + + + + + + + + Line 61:
Line 124: − Line 72:
Line 134: + + − + − − * Adopt lext on keys to current context (go vs search) Line 82:
Line 144: + + + + + + + +
Design Team/Proposals/Touchscreen/On-screen Keyboard (view source)
Revision as of 07:52, 4 September 2012
, 07:52, 4 September 2012→Build from Source on the XO
===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
Now you can run the 'maliit-keyboard-viewer' example.
There are more examples as noted under the [https://wiki.maliit.org/Documentation/Running running instructions]. You need to install 'maliit-framework-examples maliit-inputcontext-gtk3 maliit-inputcontext-gtk2' for that. And you need to update the immodues cache: 'gtk-query-immodules-3.0-32 > /usr/lib/gtk-3.0/3.0.0/immodules.cache'. Then instruct to use the Maliit IM_MODUE: 'export GTK_IM_MODULE=Maliit' and start your application:
There are more examples as noted under the [https://wiki.maliit.org/Documentation/Running running instructions]. You need to install 'maliit-framework-examples maliit-inputcontext-gtk3 maliit-inputcontext-gtk2' for that. And you need to update the immodues cache: 'gtk-query-immodules-3.0-32 > /usr/lib/gtk-3.0/3.0.0/immodules.cache'. Then instruct to use the Maliit IM_MODUE: 'export GTK_IM_MODULE=Maliit' and start your application:
maliit-exampleapp-gtk3
maliit-exampleapp-gtk3
There are many different layouts for languages like German, French, Arabic and so on, in Fedora they are stored under '/usr/share/maliit/plugins/languages/'. The format of the layouts is XML.
====Multilanguage====
There are many different layouts for languages like German, French, Arabic and so on, in Fedora they are stored under '/usr/share/maliit/plugins/languages/'. The format of the layouts is XML. Here is an example for the a [https://gitorious.org/maliit/maliit-plugins/blobs/master/maliit-keyboard/data/languages/es.xml Spanish keyboard], a [https://gitorious.org/maliit/maliit-plugins/blobs/master/maliit-keyboard/data/languages/de.xml German keyboard] and a more complex [https://gitorious.org/maliit/maliit-plugins/blobs/master/maliit-keyboard/data/languages/ar.xml Arabic keyboard]. The current selected keyboard can be seen in the Maliit gconf settings:
gconftool-2 -R /maliit
On Fedora 16/17 there is one issue where the keys that popup stay visible, this is tracked [https://bugs.maliit.org/show_bug.cgi?id=91 here].
You can change the keyboard like:
gconftool-2 --type=list --list-type string --set /maliit/onscreen/active [libmaliit-keyboard-plugin.so,es]
gconftool-2 --type=list --list-type string --set /maliit/onscreen/enabled [libmaliit-keyboard-plugin.so,es]
====Build from Source on the XO====
This has been tested on the XO 1.75 with [http://build.laptop.org/12.1.0/os13/ os 13].
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 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:
git clone git://gitorious.org/maliit/maliit-framework.git
git clone git://gitorious.org/maliit/maliit-plugins.git
Build the sources:
* First build the maliit-framework:
git checkout 0.92.4
qmake-qt4 CONFIG+=enable-dbus-activation
make
sudo make install
(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)
* Then build the maliit-plugins:
(you need HEAD here)
qmake-qt4 CONFIG+=MALIIT_DEFAULT_PROFILE=olpc-xo
make
sudo make install
* 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-2.0-32 > /usr/lib/gtk-2.0/2.10.0/gtk.immodules -->
* 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.
* 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====
* <del>I got a [http://arm.koji.fedoraproject.org/koji/getfile?taskID=743486&name=build.log&offset=-4000 build error (see as well discussion page)] and therefore build without the test 'qmake-qt4 CONFIG+=notests'.</del>
* <del>On Fedora 16/17 there is one issue where the keys that popup stay visible, this is tracked [https://bugs.maliit.org/show_bug.cgi?id=91 here].</del>
* <del>On the XO the keyboard has a fullscreen black window as background: looks like this is because we do not supports tranclucent windows and Maliit 0.91.0 needs that, according to Jon this is fixed in master</del>
===Gnome Onscreen Keyboard===
===Gnome Onscreen Keyboard===
[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===
===Previous research from Saymindu===
===Previous research from Saymindu===
[http://wiki.sugarlabs.org/go/Features/Onscreen_Keyboard Previous research from Saymindu]
[http://wiki.sugarlabs.org/go/Features/Onscreen_Keyboard Previous research from Saymindu]
===iOS===
Here you can see screnshots from the existing on screen keyboard design in [[Design_Team/Proposals/Touchscreen/On-screen_Keyboard/Examples_iOS| iOS]].
===Android===
Here you can see screnshots from the existing on screen keyboard design in [[Design_Team/Proposals/Touchscreen/On-screen_Keyboard/Examples_Android| Android Ice Cream Sandwich on an Asus TF101]].
==Evaluation==
==Evaluation==
===Needs===
===Needs===
* Multilingual text input (ability to switch at least between two languages)
* Multilingual text input (ability to switch at least between two languages)
* International (ability to show custom international characters such as accents and currency symbols)
* International (ability to show custom international characters such as accents and currency symbols)
* Frame friendly (hide frame when keyboard invoked, hide/reveal when frame is revealed/hidden)
* Frame friendly (hide frame when keyboard invoked, hide/reveal when frame is revealed/hidden)
* Sugar theme-able
* Sugar theme-able
* Insertion point movement (cursor buttons vs. left/right swipe gesture) ''This is an important one imho, I have not seen it on any other screen keyboard yet, and looked for it myself several times. On the iPad you can drag the insertion point by its tab to move the insertion point (you will get a magnifier), to pick exactly where you want to add more text. This works in the notes taking app and in Safari. In Android I have seen the same working in the Browser, but not in Polaris Office for example."
* Subtle keyclick sound effect to provide positive feedback for text entry
===Would like to haves===
===Would like to haves===
* Adopt text on keys to current context (go vs search)
* Insertion point movement (cursor buttons vs. left/right swipe gesture) ''This is an important one imho, I have not seen it on any other screen keyboard yet, and looked for it myself several times. On the iPad you can drag the insertion point by its tab to move the insertion point (you will get a magnifier), to pick exactly where you want to add more text. This works in the notes taking app and in Safari. In Android I have seen the same working in the Browser, but not in Polaris Office for example."
* Additional customisable key/button strips for Activities to provide additional specific features
* Additional customisable key/button strips for Activities to provide additional specific features
* Keys for cut/copy/paste – perhaps toolbar buttons are enough already?
* Keys for cut/copy/paste – perhaps toolbar buttons are enough already?
* 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==