[Uim] Using Subwindow & IM Specific widget.

[TOKUNAGA Hiroyuki]

On Sat, 11 Dec 2004 13:05:48 +0900
Kazuki Ohta <mover at hct.zaq.ne.jp> wrote:

> Recently, PRIME(Predictable Input Method Engine) 0.8.5 and 0.9.3 was
> released. New version of PRIME has the impressive function that can
> show the use case of the preedit string. 
> 
> Screen Shot:
> http://www.geocities.jp/ep3797/snapshot/tmp/prime-0.9.3-01.png
> 
> Now usecase is shown by using candidate window(in scim, lookuptable),
> but I think this is not the proper place. So I want to implement the
> "subwindow" to show the extra information of candidates or preedit.
> This is what like this.
> 
> Screen Shot: 
> http://mover.cool.ne.jp/others/uim/2004-10-15-1097826815_1024x768_scrot.png
> 
> To achieve this, I came up with two implementation ways.
> 1. Using callback
> export (im-activate-subwindow) and (im-deactivate-subwindow) to IMs,
> and export (uim_set_subwindow_cb) to frontends.

I don't want to add new API for usecase.

> 2. Add variable to candidate data struct
>    struct uim_candidate_ {
>        char *str;         /* candidate */
>        char *heading_label;
>        char *annotation;
> 
>        char *subwindow_data;
>    };

I prefer this. But use annotation member instead of adding new member.

> And the Komatsu-san, the author of PRIME also requested to use the
> widget for registering the words to the dictionary. This is
> IM-specific widget, so creating public API for this purpose is a bit
> odd. So I suppose excuting other APP like this seems good for me.
> 
> (im-activate-widget "prime-dictregister-dialog" "args")
> (im-deactivate-widget "prime-dictregister-dialog")

Basically OK, but

  - the word 'widget' is confusing
  - deacticate wouldn't need.

I think simple scheme interface for execl is enough.


Regards,

-- 
TOKUNAGA Hiroyuki
http://kodou.net/