On Tue, Dec 05, 2006 at 10:11:07PM +0800, ZhengPeng Hou wrote: > On Tue, Dec 05, 2006 at 08:20:25PM +0000, Wen-Yen Chuang wrote: > > > > [2] For example, gcin's im-switch script enables Qt3 immodule > > automatically, when it found libqgcin.so. If the user remove > > gcin-qt3-immodule, then XIM will be used as the fallback default. > > > Maybe we can set this in scim's conffile for im-switch, then it can > use scim-qtimm/scim-bridge-client-qt automatically, according to guys > install any of them, if they haven't install any, then it will use xim > defaultly.
I know that Ubuntu's scim uses this approach, which checks the existence of the GTK/Qt IM module at runtime and changes the im-switch setting accordingly. I haven't looked at Debian's gcin yet, but I assume it does a similar thing. I am still not convinced that this is the right way to go. I really don't like scripts changing behaviors just because a newly installed or removed package. This also makes a user with GTK/Qt IM module installed impossible to use XIM instead. Currently Debian's scim uses two different im-switch settings, one with XIM, the other with GTK/Qt IM module (although the Qt settings are not enabled yet), and users can use im-swtich to choose between these two. This approach has its own problem (more maintenance, more confusion to the user, etc.), but I still like it better. Ming 2006.12.06 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
