Age | Commit message (Collapse) | Author | Files | Lines |
|
BUG=http://code.google.com/p/ibus/issues/detail?id=1671
TEST=client/wayland/ibus-wayland
Review URL: https://codereview.appspot.com/18780044
Patch from Eduardo Lima (Etrunko) <eduardo.lima@intel.com>.
|
|
Using ssh -X or another display, the hostname and display numbers
can be different between the GTK clients and ibus-daemon.
This patch fixes the output:
"Events queue growing too big, will start to drop."
BUG=RH#1004135
TEST=clients/gtk*/im-ibus.so
Review URL: https://codereview.appspot.com/13707046
|
|
TEST=password dialog in gnome-shell
Review URL: https://codereview.appspot.com/13255047
|
|
Add a new D-Bus method SetContentType to InputContext and Engine, to
notify engines of the content-type (primary purpose and hints) of
input context. This is useful to implement intelligent features in
engines, such as automatic input-mode switch and text prediction.
The "purpose" and "hints" arguments are compatible with
GtkInputPurpose and GtkInputHints:
https://developer.gnome.org/gtk3/unstable/GtkEntry.html#GtkInputPurpose
https://developer.gnome.org/gtk3/unstable/GtkEntry.html#GtkInputHints
and the API is similar to the content_type event in the Wayland Input
Method Framework:
http://cgit.freedesktop.org/wayland/weston/tree/protocol/input-method.xml#n202
BUG=
Review URL: https://codereview.appspot.com/11422043
|
|
This patch adds a new client which supports the Wayland input method
protocol. Note that the support is disabled by default until the
input method protocol becomes official in the Wayland upstream.
Supply --enable-wayland to configure to try it. Also, you will need
to set the executable path of ibus-wayland under the "input-method"
section of weston.ini, like this:
[input-method]
path=.../libexec/ibus-wayland
BUG=Issue#1617
Review URL: https://codereview.appspot.com/11320043
Patch from Jan Arne Petersen <jan.petersen@kdab.com>.
|
|
BUG=http://code.google.com/p/ibus/issues/detail?id=1424
TEST=rpmlint
Review URL: https://codereview.appspot.com/12526043
|
|
The make variable INCLUDES is now obsoleted by AM_CPPFLAGS.
BUG=
R=Shawn.P.Huang@gmail.com
Review URL: https://codereview.appspot.com/9915054
|
|
Recent GtkIMContext has "input-purpose" property, which can be used to check if the target widget is a password entry, in a more reliable way.
BUG=none
R=Shawn.P.Huang@gmail.com
Review URL: https://codereview.appspot.com/7064059
|
|
BUG=None
TEST=Manual
Review URL: https://codereview.appspot.com/7531047
|
|
There are actually 3 patches here.
---
client: Queue events while the IBus context isn't ready
We may lose events that ought to be processed while the IBus context
isn't ready or if the connection to IBus isn't fully established yet.
To avoid that, enqueue events to be processed later when the IBus
context creation finishes.
---
client: Don't cancel an ongoing create input context on another request
This would only add more delays.
---
client: Cancel any ongoing create input context request on finalize
BUG=
Review URL: https://codereview.appspot.com/6988047
Patch from Rui Matos <tiagomatos@gmail.com>.
|
|
BUG=None
Review URL: https://codereview.appspot.com/6623048
|
|
BUG=RH#859879
TEST=Manually
Review URL: https://codereview.appspot.com/6573051
|
|
some multi-threaded apps.
BUG=http://code.google.com/p/ibus/issues/detail?id=1505
Review URL: https://codereview.appspot.com/6488104
|
|
BUG=http://code.google.com/p/ibus/issues/detail?id=1489
Review URL: https://codereview.appspot.com/6454158
|
|
BUG=http://code.google.com/p/ibus/issues/detail?id=1452
TEST=Manually
Review URL: https://codereview.appspot.com/6198052
Patch from Jason Conti <jason.conti@gmail.com>.
|
|
IMForwardEvent() calls _Xi18nFindClient() and it could return NULL.
Maybe the connect_id would be disconnected during the async
process_key_event.
This fix checks XIM_DISCONNECT in ims_protocol_handler() to cancel
IMForwardEvent() in _process_key_event_done().
BUG=RH#769135
TEST=Linux desktop
Review URL: https://codereview.appspot.com/5498090
|
|
BUG=None
TEST=Make
Review URL: https://codereview.appspot.com/5756061
|
|
|
|
BUG=None
TEST=None
Review URL: https://codereview.appspot.com/5618046
|
|
Remove .gitignore files from the git repo, define GITIGNOREFILES in some
Makefiles, and update git.mk from the Behdad upstream.
BUG=none
TEST=manually
Review URL: https://codereview.appspot.com/5581057
|
|
BUG=
TEST=Linux desktop
Review URL: http://codereview.appspot.com/5489086
|
|
BUG=https://code.google.com/p/ibus/issues/detail?id=1358
TEST=On Fedora with ibus-m17n tis820
Review URL: http://codereview.appspot.com/5431086
|
|
ibus-hangul calls ibus_commit_text() in process_key_event with
returing FALSE. ibus_commit_text() is async API and there is a
time issue in ibus_commit_text() and returning process_key_event.
This fix adds async in ibus-x11 process_key_event too.
BUG=RH#753781
TEST=Linux desktop
Review URL: http://codereview.appspot.com/5417044
|
|
For an old bug:
https://bugzilla.redhat.com/show_bug.cgi?id=484643
Input method should be disabled on password entry for security reason.
BUG=none
TEST=manually with gtk-demo "Entry Buffer" example
Review URL: http://codereview.appspot.com/5319053
|
|
This patch enable us to get selection text on client application.
Currently only GtkTextView widget can get them in gtk application.
BUG=None
TEST=manually done.(By gedit text editor)
Review URL: http://codereview.appspot.com/4844041
Patch from Seigo Nonaka <nona@chromium.org>.
|
|
Forget include config.h in gdk-private.c. So the HAVE_X11_XKBLIB_H is always undefined, and ibux-x11 can not get correct group from x key event.
BUG=ibus-x11 can not handle group correctly
TEST=Linux desktop
Review URL: http://codereview.appspot.com/4865041
|
|
Due to the asynchronous creation of contexts, gtk_im_set_use_preedit may
be called before the context is ready. This patch is to
record the change of capability flag and enables to set it
later in _create_input_context_done.
BUG=http://crosbug.com/16500
TEST=ChromeOS Cr-48
Review URL: http://codereview.appspot.com/4635049
Patch from Kazuhiro Inaba <kinaba@chromium.org>.
|
|
Currently the immodule tries to retrieve surrounding-text unconditionally
on focus_in and enabled. These calls could be eliminated if engine were
able to proclaim that it will need surrounding-text.
This patch extends ibus_engine_get_surrounding_text() to allow this.
Engines that need surrounding-text are expected to have:
/* Indicate we will use surrounding-text. */
ibus_engine_get_surrounding_text (engine, NULL, NULL);
in their enable() method. This would work because enable() is called before
SetCapabilities DBus call.
BUG=none
TEST=manually with ibus-m17n, with the above change.
Review URL: http://codereview.appspot.com/4613043
Patch from Daiki Ueno <daiki.ueno@gmail.com>.
|
|
BUG=http://crosbug.com/16500
TEST=Linux desktop
Review URL: http://codereview.appspot.com/4635044
|
|
BUG=None
TEST=Test on Linux desktop
Review URL: http://codereview.appspot.com/4517146
|
|
BUG=Build warnings with gcc 4.6
TEST=Manually
Review URL: http://codereview.appspot.com/4517127
|
|
BUG=none
TEST=none
Review URL: http://codereview.appspot.com/4529103
|
|
Review URL: http://codereview.appspot.com/4440060
|
|
BUG=none
TEST=Linux desktop
Review URL: http://codereview.appspot.com/4365049
|
|
Unlike the GtkIMContext API, IBus automatically retrieves
surrounding-text when certain events occurred to the
client ("before filter_keypress", for example). This makes the
engine API simpler but causes periodical emission of D-Bus
signals for updating surrounding-text information, which is
unwanted for typical engines.
For this reason, the surrounding-text support is currently
disabled by default. To enable it, pass
--enable-surrounding-text to configure. Also, even
surrounding-text support is compiled in, IBus does not start
polling until an engine requests surrounding-text using
ibus_engine_get_surrounding_text(). To make the function work
for the first time, clients should retrieve
initial surrounding-text when the engine is enabled (see ibus_im_context_focus_in() and
_ibus_context_enabled_cb() in client/gtk2/ibusimcontext.c).
BUG=Issue#778
TEST=manual
Review URL: http://codereview.appspot.com/4276082
Patch from Daiki Ueno <daiki.ueno@gmail.com>.
|
|
Replace some block IPC calls with async IPC calls, and then IBusIMContext will
not block UI anymore.
BUG=http://crosbug.com/12310
TEST=Linux desktop
Review URL: http://codereview.appspot.com/4287054
|
|
BUG=none
TEST=make
Review URL: http://codereview.appspot.com/4280050
|
|
|
|
Review URL: http://codereview.appspot.com/4261056
|
|
BUG=http://crosbug.com/12803
TEST=Linux desktop
Review URL: http://codereview.appspot.com/4267044
|
|
focus_in calls some X blocking functions. It will block UI. This change delays the X blocking calls to idle callback, to avoid blocking UI.
BUG=http://crbug.com/74237
TEST=Linux desktop
Review URL: http://codereview.appspot.com/4254048
|
|
BUG=none
TEST=Linux desktop
Review URL: http://codereview.appspot.com/4246042
|
|
|
|
BUG=none
TEST=Linux desktop
Review URL: http://codereview.appspot.com/4178062
|
|
|
|
|
|
BUG=chromium-os:11421
TEST=manually done on Chrome OS.
Review URL: http://codereview.appspot.com/3989060
|
|
Some application may want to integrate with ibus directly, and want to
use async mode for processing key events. So I make
ibus_input_context_process_key_event to be an async function,
and also added ibus_input_context_process_key_event_sync.
Fix problem in introspection of Engine.
BUG=none
TEST=Tested in Ubuntu 10.10
Review URL: http://codereview.appspot.com/4032044
|
|
|
|
From the git log of gtk3, they started adding _KEY from 2.91.0 not 2.90.0.
BUG=none
TEST=manual
Review URL: http://codereview.appspot.com/3670041
|