Design Team/Proposals/Touchscreen/On-screen Keyboard - Revision history

Erikos: /* Build from Source on the XO */

2012-09-04T11:52:46Z

Build from Source on the XO

← Older revision		Revision as of 07:52, 4 September 2012
Line 73:		Line 73:
	You can add as well several languages to be available:		You can add as well several languages to be available:

	./maliit-exampleapp-settings-python3.py set enabled libmaliit-keyboard-plugin.so:ar,libmaliit-keyboard-plugin.so:de		./maliit-exampleapp-settings-python3.py set enabled libmaliit-keyboard-plugin.so:en_gb,libmaliit-keyboard-plugin.so:de

	====Issues====		====Issues====

Erikos: /* Build from Source on the XO */

2012-09-03T12:58:15Z

Build from Source on the XO

← Older revision		Revision as of 08:58, 3 September 2012
Line 73:		Line 73:
	You can add as well several languages to be available:		You can add as well several languages to be available:

	./maliit-exampleapp-settings-python3.py set enabled		./maliit-exampleapp-settings-python3.py set enabled libmaliit-keyboard-plugin.so:ar,libmaliit-keyboard-plugin.so:de
	libmaliit-keyboard-plugin.so:ar,libmaliit-keyboard-plugin.so:de

	====Issues====		====Issues====

Erikos: /* Build from Source on the XO */

2012-09-03T12:51:30Z

Build from Source on the XO

← Older revision		Revision as of 08:51, 3 September 2012
Line 49:		Line 49:
	make		make
	sudo make install		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:		* Then build the maliit-plugins:

Erikos: /* Build from Source on the XO */ added steps to change the style

2012-09-03T12:48:03Z

Build from Source on the XO: added steps to change the style

@@ Line 62: / Line 62: @@
 * 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.
 ====Issues====

Erikos: /* Build from Source on the XO */

2012-08-23T13:33:22Z

Build from Source on the XO

← Older revision		Revision as of 09:33, 23 August 2012
Line 45:		Line 45:
	Build the sources:		Build the sources:
	* First build the maliit-framework:		* First build the maliit-framework:
	git checkout 0.92.1		git checkout 0.92.4
	qmake-qt4 CONFIG+=enable-dbus-activation		qmake-qt4 CONFIG+=enable-dbus-activation
	make		make

Cjl: /* Florence */

2012-08-23T03:27:40Z

Florence

← Older revision		Revision as of 23:27, 22 August 2012
Line 71:		Line 71:
	[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===

FGrose: /* Advancements */

2012-08-23T03:25:29Z

Advancements

← Older revision		Revision as of 23:25, 22 August 2012
Line 137:		Line 137:
	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.		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. --[[User:FGrose\|FGrose]] 23:09, 22 August 2012 (EDT)		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==

FGrose: /* Advancements */

2012-08-23T03:12:51Z

Advancements

← Older revision		Revision as of 23:12, 22 August 2012
Line 135:		Line 135:
	==Advancements==		==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 at the same time.		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. --[[User:FGrose\|FGrose]] 23:09, 22 August 2012 (EDT)		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. --[[User:FGrose\|FGrose]] 23:09, 22 August 2012 (EDT)

	==Recommendation==		==Recommendation==

FGrose at 03:09, 23 August 2012

2012-08-23T03:09:39Z

← Older revision		Revision as of 23:09, 22 August 2012
Line 132:		Line 132:
	* 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 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. --[[User:FGrose\|FGrose]] 23:09, 22 August 2012 (EDT)

	==Recommendation==		==Recommendation==

Erikos: /* Build from Source on the XO */

2012-08-10T14:06:09Z

Build from Source on the XO

← Older revision		Revision as of 10:06, 10 August 2012
Line 51:		Line 51:

	* Then build the maliit-plugins:		* Then build the maliit-plugins:
	~~git checkout 0.92.1~~		(you need HEAD here)
	qmake-qt4 CONFIG+=MALIIT_DEFAULT_PROFILE=olpc-xo		qmake-qt4 CONFIG+=MALIIT_DEFAULT_PROFILE=olpc-xo
	make		make