[openi18n-im:01481] Re: Announcement: iiim Palette function works now

Kasha,

Yes, the implementation breaks the compatibility, it would be great that
you can work with Phill to come up one alternative to completely resolve
this issue ASAP.

In my opinion, if the above goal can't be achieved, we have to make
decision which one does matter the most
*at current situation*: compatibility vs cool feature. Of course, we
should do our best to avoid compatibility being
broken, but we can't wait here, a lot of important features are ahead of
us:

    Unified configuration window (plus hotkey configuration)
    Common language engine
       LEIF2
       Common AUX: candidate and pre-edit window

-federic


> Phill,
> 
> Good work for the new feature!
> 
> 
> Phill and All,
> 
> Unfortunately the implementation breaks the compatiblity in
> IIIMP and libiiimp.so.  So I will revert the trunk to r2767 to
> avoid any compatibility problem.  I will directly discuss Phill
> how this issue can be solved and the feature comes back again.
> 
> Thanks,
> -- 
> kasha
> 
> Date: Tue, 12 Jul 2005 14:06:12 +0800
> From: Lei Phill Zhang <[email protected]>:
> > I will give more document later.
> > 
> > > Hi,
> > > 
> > > Date: Mon, 11 Jul 2005 15:23:54 +0800
> > > From: Lei Phill Zhang <[email protected]>:
> > > > 
> > > >     As mentioned two weeks ago, the palette function which
> > > > using the dynamic Gui Builder to render some IME properties
> > > > is working well now. Yet some extra works need to be done
> > > > recently:
> > > >     1. merge with current open-i18n trunk
> > > >     2. add support in iiimxcf, iiimqcf, (i.e., any other than gcf)
> > > >     3. Add focus-in/focus-out wrong sequence trick in Palette window.
> > > 
> > > Would you write down a protocol specification for the feature?
> > > And would you explain what components are involved, and how
> > > components interact each other?  Details are appreciated.
> > > 
> > > Thanks,
> > > -- 
> > > kasha
> > > 
> > > > 
> > > > Middle term goals maybe:
> > > >     1. combine with gimlet, (such as integrate language/IM switching,
> > > > mapping / unmapping to the notification area, etc)
> > > >     2. Finishing configuration window using current dynamic GUI builder
> > > > API
> > > >     3. Porting several sample LE by using the palette.
> > > > 
> > > > Long term goals maybe:
> > > >     1. neuture common aux framework.
> > > >     2. more easy to use API for these in LEIF tier2.
> > > > 
> > > >     The code is in our local CVS repository. And after the code
> > > > merge work is done, we will asking for code review and commit.
> > > > 
> > > > 
> > > > Best Regards
> > > > Phill Zhang