Gaia/System/Keyboard/Layout: Difference between revisions

From MozillaWiki
< Gaia‎ | System‎ | Keyboard
Jump to navigation Jump to search
(Replaced content with "This document have been moved to [https://developer.mozilla.org/en-US/Firefox_OS/Developing_Gaia/Customizing_the_keyboard MDN]. [https://wiki.mozilla.org/index.php?title=...")
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This document explains how to add custom keyboard layouts containing their own languages/scripts to '''Firefox OS v1.2''' and up.
This document have been moved to [https://developer.mozilla.org/en-US/Firefox_OS/Developing_Gaia/Customizing_the_keyboard MDN].


== Status of the Gaia Keyboard app & system architecture ==
[https://wiki.mozilla.org/index.php?title=Gaia/System/Keyboard/Layout&action=history History of this page].
 
Two major features have been implemented in Firefox OS, as of October 2013.
 
* A build flag to turn keyboard/spellcheck dictionaries to include in the build in the default Gaia Keyboard app on and off (see {{Bug|884752}}).
* An OS-level feature that allows users to install 3rd-party keyboard apps from the Firefox Marketplace. See {{Bug|816869}}.
 
To come up with a new keyboard layout, you can put a layout file in Gaia, build the keyboard app using a build config, or come up with your own keyboard app and install it on the phone.
 
== How to make a keyboard app ==
 
You can use Gaia's built-in keyboard app as a template, or fork it. The basic ideas are:
 
* In the manifest file, declare your keyboard in the <code>role</code> property.
* Make sure you have the <code>input</code> permission specified.
 
After that, you can install your keyboard, and it will show up on the bottom half of the screen whenever the user is focused to a input field. The space issues that arise from this can be dealt with by:
 
* Using the old, classic <code>window.resize</code> to update the area of your app should occupy.
* Using the new, shiny <code>navigator.mozInputMethod</code> API to mutate the content of the input given; see the [[WebAPI/KeboardIME|KeyboardIME API page]] for details.
 
TBD: provide sample code and/or a small template app
 
== How to add a custom layout to your template in the Gaia keyboard app ==
 
See [https://github.com/mozilla-b2g/gaia/blob/master/apps/keyboard/CONFIGURE apps/keyboard/CONFIGURE] for details. Depending on the language you might want to add a dictionary, or include an interactive IME (for Asian languages).
 
=== Spell check / word suggestion dictionary ===
 
(TBA)
 
=== Asian IME ===
 
==== Introduction ====
 
East Asian languages (Chinese, Japanese, and Korean) use [https://en.wikipedia.org/wiki/CJK a fairly complex script] that involves thousands of characters. As there is no way to put thousands of keys on a hardware or software keyboard, users rely on an indexing program called [https://en.wikipedia.org/wiki/Input_method input method], or IME for short, to convert series of symbols into selections of characters.
 
How symbols should be converted and how "smart" the IME should be depends on the method chosen, implementation itself, and often [https://en.wikipedia.org/wiki/Natural_language_processing NLP] science, which is outside the scope of this document. One thing to note is that it is highly recommended to put the database part into IndexedDB, in order to conserve memory on a mobile device.
 
==== IM Engine interface in Gaia keyboard app ====
 
Assuming you have an IME library readily available for converting symbols into characters (''IM Engine'' in our terminology), you would need to use the defined interface within the Gaia Keyboard app to receive symbols from the layout and output the characters. The [https://github.com/mozilla-b2g/gaia/blob/master/apps/keyboard/js/keyboard.js#L32-L115 current API is documented on Github].
 
We invite implementations in order to further refine this API within Gaia.
 
==== Make your IM engine work with your layout ====
 
To get your IM engine working with your keyboard layout:
 
# Put a new layout in layout.js as described in the previous section.
# Reference the IM engine with the <code>imEngine</code> property. When your layout is enabled, the keyboard app will start loading the script located at <code>keyboard/js/imes/<imEngine>/<imEngine>.js</code>.
# Set up the APIs to receive and send the keys/characters when the script is loaded and <code>init</code>'d.
# Do whatever you want in response to the user input. When the user taps any keys on the keyboard, it would typically get sent to the IM engine.
 
==== Known implementations ====
 
* [https://github.com/timdream/jszhuyin JSZhuyin] is the first implementation of Gaia Keyboard Asian IM engine, for Traditional Chinese incorporating Zhuyin IME.
* [https://github.com/mozilla-b2g/gaia/tree/master/apps/keyboard/js/imes/jskanji JSKanji] is a prototype IM engine written for Japanese.
* [https://github.com/mozilla-b2g/gaia/tree/master/apps/keyboard/js/imes/jspinyin JSPinyin] is a written for Simplified Chinese and works by tapping Pinyin symbols.
* As a demonstration, [http://chewing.csie.net/ Chewing], an C/C++ open-source Zhuyin IME for Traditional Chinese, was [https://bugzilla.mozilla.org/show_bug.cgi?id=845685 cross-compiled with emscripten] and linked with the Gaia keyboard.
* [https://bugzilla.mozilla.org/show_bug.cgi?id=835261 JSHangul] is a prototype IM engine for Korean, and is currently in development.
 
== Discussion, Q&A, etc ==
 
Please come to the [https://lists.mozilla.org/listinfo/dev-gaia dev-gaia] mailing list or the <code>#gaia</code> channel on irc.mozilla.org. <code>#mozilla-taiwan</code> is the de-facto Chinese-language channel for this topic.

Latest revision as of 02:36, 17 August 2014

This document have been moved to MDN.

History of this page.

Retrieved from "https://wiki.allizom.org/index.php?title=Gaia/System/Keyboard/Layout&oldid=1006338"