Re: How is the text data been send to say GTK Entry in SCIM?

[Peng Wu]

On Sat, 2009-01-24 at 14:34 +0800, Liu, Raymond wrote:
> Hi
> Pardon me for the silly question.
         Not silly, but difficult to answer. Correct me, if something is
wrong.
> I just start to look into the Input method on Linux.
> I can see that SCIM using gtkimcontext to communicate with GTK widgets. While I read the API for GTKIMContext, I can see there are focus_in, focus_out etc. But I fail to see and API say send the text it self to the editable widget. So I am wondering how is this been done (Especially for CJK?)
>
> Is that still need XIM protocol to send xevents to the X and then to GTK widget?
> Or directly call the widget's method, something like GTKEntry.settext(xxx) ?
         When any gtk im module want to change the preedit string, it
should emit signals "preedit-changed", "preedit-start", "preedit-end".
         When any gtk im module want to commit string to widget, it
should emit signal "commit".

         When your gtk applications use gtk xim im module, it will use
XIM to communicate to scim.
         When your gtk applications use gtk scim/scim-bridge im module,
it will by pass the XIM, using socket instead. Also if you write a
custom im module, you can use any thing you want to deal with the input
key codes.

>
> Can anyone kindly help me to understand it?
>
> Best Regards,
> Raymond Liu
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Scim-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/scim-devel

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Scim-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/scim-devel

[Liu, Raymond]

Hi Wu Peng

>> Hi
>> Pardon me for the silly question.
>         Not silly, but difficult to answer. Correct me, if something is
>wrong.

Thanks for your reply :)

>> Is that still need XIM protocol to send xevents to the X and then to GTK widget?
>> Or directly call the widget's method, something like GTKEntry.settext(xxx) ?
>         When any gtk im module want to change the preedit string, it
>should emit signals "preedit-changed", "preedit-start", "preedit-end".
>         When any gtk im module want to commit string to widget, it
>should emit signal "commit".
>

So scim-bridge-client-gtk is actually a gtk im module which communicate with the agent side and eventually it will emit signals which can be accepted by GTK, is that right?

So, Say if I want to implement another im module for the other UI framework, then it must already have some similar mechanism like gtk-imcontext, right?

>         When your gtk applications use gtk xim im module, it will use
>XIM to communicate to scim.
>         When your gtk applications use gtk scim/scim-bridge im module,
>it will by pass the XIM, using socket instead. Also if you write a
>custom im module, you can use any thing you want to deal with the input
>key codes.

I can see that except im-scim-bridge.so, there is also im-scim which is belonging to the scim package. So what's the different of these two IM modules?

Raymond


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Scim-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/scim-devel