[openi18n-im:01291] Re: Need API change: iiimcf_retrieve_hotkeys () and IIIMCF_EVENT_TYPE_REGISTER_HOTKEYS

Tajima-san,

No problem at all and thanks a lot for your efforts. Actually Sriram has just 
contacted me as well regarding on his part needs to do some API changes as 
well by today. 

It seems that 10 days between the feature freeze may not be ideal for 
contributors compared to what we discussed this schedule initially. Apologies 
on this.

If there aren't any developers (LE and libraries) object this because it may 
interfere with ones development, let's extend the API freeze until 15th, 
March. However code freeze will stay as planned - 22nd April 2005.

But as far as I can see on the svn commit movement, we are still on track. 
Wonderful work around the table! Thank you to be a part of fine-tuning the 
schedule and process.

Cheers,
Leon

On Friday 11 March 2005 17:36, Hidetoshi Tajima wrote:
> Hi Leon, and all,
>
> I'm afraid I'm the 1st to propose an API change after the freeze.
>
> But, I'd need an API in libiiimcf to retrive hot key list, and
> possibilly a new IIIMCF event,
> IIIMCF_EVENT_TYPE_REGISTER_HOTKEYS.
>
> This is for xiiimp.so.2 and htt_xbe to achieve dynamic event flow model
> with XIM
> applications, where ximcp.so.2 or old ximp40.so.2 is used in XIM
> implementation,
> and they will need to receive conversion start up keys through XIM protocol
> as soon as the connection with XIM server is made.
>
> The new API will be to pull hot keys:
>
>    #include <iiimcf.h>
>    extern iiimcf_get_hotkeys (IIIMCF_context context, int *num_hotkey,
> IIIMCF_keyevent
>          *keys);
>
> This may be called when a new context is created, or when new IIIMCF
> event  IIIMCF_EVENT_TYPE_REGISTER_HOTKEYS is dispatched.
>
> I'll create a prototype for proof of concept, and come up again with
> complete API and
> patches for libiiimcf and xiiimp.so.2 - no later than 03/15 (Tue).
>
> Regards,
> Toshi
>
> Leon Ho wrote:
> >All,
> >
> >Reminder the freeze is on 10 March 2005. Commit to either svn or with
> > change proposal. This will ensure third party vendors and LE developers
> > can use the existing code without breaking their code on the rest of
> > development cycle.
> >
> >Regards,
> >Leon
> >
> >San Fransisco 06:00
> >New York 09:00
> >Pune 07:30
> >Beijing 22:00
> >Tokyo 23:00
> >Brisbane 00:00 (+1day)