Updates:
Labels: -Type-Defect Type-Enhancement
Comment #1 on issue 1235 by [email protected]: [feature request] Add a
gsettings backend
http://code.google.com/p/ibus/issues/detail?id=1235
I also think it would be nice if we could switch, but it might be a bit too
drastic change to ibus IMEs, because:
- gsettings enforces schemas on client data, while ibus IMEs do not
- gsettings only accepts key names consisting of [-a-z0-9], while ibus and
IMEs use upper-case letters and "_" extensively
As a starting point, I created an experimental ibus-dconf backend, which is
mostly compatible with the current ibus config, but saves data in dconf db
(which gsettings reads):
https://github.com/ueno/ibus/commit/4fcd135c
A known drawback is that, it converts key names to gsettings-acceptable
ones when get/set but cannot convert back on "value-changed" signal.
--
You received this message because you are subscribed to the Google
Groups "ibus-devel" group.
iBus project web page: http://code.google.com/p/ibus/
iBus dev group: http://groups.google.com/group/ibus-devel?hl=en