Let say that I'm trying to learn Korean (or another no "popular" language) and brought a device with Firefox OS that didn't came with the keyboard for such language to save space. As a user, will be awesome if I can install the official keyboard for any language from Marketplace.
Quite interesting. May we could consider to add it to the official Makefile?
Assignee: nobody → salva
Before we got bug 1029951 fixed, I think it is reasonable to have one big keyboard app on marketplace that includes all the keyboard layouts/dictionaries. If we have this, we don't have to change the Makefile and everyone can install that single app, right? However, it would still need some work to get the built-in keyboard app onto marketplace, at least we should get rid of the mozSettings related part.
See Also: → 1029951
(In reply to Rudy Lu [:rudyl] from comment #3) > However, it would still need some work to get the built-in keyboard app onto > marketplace, at least we should get rid of the mozSettings related part. Nice catch. Keyboard app would be smart enough to turn to, maybe, asyncStorage when it is being run as a privileged app. It not a hard work but we need to be careful not to break anything.
The problem with asyncStorage is you can not emulate `addObserver()` but we can use localStorage as in my shim for mozSettigs  as a replacement. Notice the penalty of using localStorage is negligible given the amount of data being stored and the unique feature it shows: the storage event is broadcasted to all open window.  https://github.com/lodr/shimmozsettings
Do you have any inconvenient with adding Raniere's tool to split the keyboard into different per-layout applications? How can we advance on this bug?
Hi Salva, Could you be more specific about your question? Which part in this bug would need me to look into? Thanks.
Hi Rudy, I was referring to include the tool provided in comment 1 into the Gaia's build system. This allow us to split the keyboard into separated apps, once per layout. Of course, it repeats the keyboard code and it could be not the optimal way to do it. I don't know if there are other alternatives to provide independent and plug-able layouts for the keyboard.
Firefox OS is not being worked on
Status: UNCONFIRMED → RESOLVED
Closed: Last year
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.