Merge xkb related changes.

Merge xkb related changes.
This CL renames the config name of hotkeys:
prev_engine -> previous_engine
next_engine -> next_engine_in_menu

Following new configs are added:
general/global_engine
general/global_previous_engine
general/enable_by_default

We should sync the first two configs to cloud. The third one is not useful for us, as it should be TRUE by default.

I know that libcros and chrome should be fixed to adapt these new values. I'll send out another CL to fix them and submit these CLs at the same time.

Not sure if it's ok to update two dependent parts separately. Seems that there is no way to update them at once.




Merge branch 'xkb-integration' into merge-xkb-integration


Merge branch 'master' into xkb-integration


Fix ui to support basic xkb layout switching.


Fix enable_by_default thing.


Add enable_by_default config. When it's true then the newly created input context will be enabled by default.


XKB integration 2nd version - part 1.

[Yusuke Sato, 2010-04-23 03:09:09]

Thanks for the change! I have one question:

We're not using the python binding for ibus as you know. Isn't it possible to
merge only C files to make it easier to merge upstream changes?

On 2010/04/23 01:31:58, James Su wrote:
>

[Yusuke Sato, 2010-04-23 03:47:42]

> We should sync the first two configs to cloud.

You might have to modify 6 files in Chrome tree: pref_names.{cc,h},
preferences.{cc,h}, language_preferences.h, and synchronized_preferences.h to
support the new prefs. I think http://codereview.chromium.org/1631030 would be a
good example.

And FYI, I asked Zack (zork, who's been working on Sync) if it's safe to remove
prefs from chrome/browser/sync/glue/synchronized_preferences.h and he said it
should be okay. So please remove prefs::kLanguageHotkeyNextEngine and
prefs::kLanguageHotkeyTrigger from the header file when your new hot keys get
ready.


> I'll send out another CL to fix them and submit these CLs at the same time.
> Not sure if it's ok to update two dependent parts separately. Seems that there
is no way to update them at once. 

For Chrome OS official releases, Chrome binary and Chrome OS userland are built
separately. This means that older Chrome browser binary could be used with newer
Chrome OS userland (i.e. libcros and libibus). So I'm afraid that submitting all
3 changes at once might not work.

However, libcros has a simple ABI versioning feature which is supposed to detect
bad combinations of Chrome browser and libcros. You might want to use this (see
documentation in src/platform/cros/chromeos_cros_api.h for details.)

Anyway, I'd like to review CLs for Chrome and libcros first :)

Thanks!

[James Su, 2010-04-23 18:50:37]

On 2010/04/23 03:09:09, Yusuke Sato wrote:
> Thanks for the change! I have one question:
> 
> We're not using the python binding for ibus as you know. Isn't it possible to
> merge only C files to make it easier to merge upstream changes?
I'd like to keep them for testing purpose. Also, I'm pushing all of these
changes into upstream.

> 
> On 2010/04/23 01:31:58, James Su wrote:
> >

[Yusuke Sato, 2010-04-23 18:53:11]

I see. Then I'm fine with merging py files.

On 2010/04/23 18:50:37, James Su wrote:
> On 2010/04/23 03:09:09, Yusuke Sato wrote:
> > Thanks for the change! I have one question:
> > 
> > We're not using the python binding for ibus as you know. Isn't it possible
to
> > merge only C files to make it easier to merge upstream changes?
> I'd like to keep them for testing purpose. Also, I'm pushing all of these
> changes into upstream.
> 
> > 
> > On 2010/04/23 01:31:58, James Su wrote:
> > >

[Yusuke Sato, 2010-04-26 18:19:33]

(Discussed with James and he said he would modify the change so that it would
not break backward compatibility.)

On 2010/04/23 18:53:11, Yusuke Sato wrote:
> I see. Then I'm fine with merging py files.
> 
> On 2010/04/23 18:50:37, James Su wrote:
> > On 2010/04/23 03:09:09, Yusuke Sato wrote:
> > > Thanks for the change! I have one question:
> > > 
> > > We're not using the python binding for ibus as you know. Isn't it possible
> to
> > > merge only C files to make it easier to merge upstream changes?
> > I'd like to keep them for testing purpose. Also, I'm pushing all of these
> > changes into upstream.
> > 
> > > 
> > > On 2010/04/23 01:31:58, James Su wrote:
> > > >