[immodule-qt] introducing QT_IM_SWITCHER environment variable

[YamaKen]

Hi Takumi, thank you for respoonding.

At Tue, 17 Aug 2004 19:10:02 +0900,
takumi at asaki.jp wrote:
> On Tuesday 10 August 2004 17:02, YamaKen wrote:
> 
> > > It confuses ordinary users. Although ordinary users will not
> > > imagine such configuration, weird users will favor such
> > > configuration and publish their configuration memo to the
> > > world. It will confuse victims that googled with 'QT_IM_MODULE'.
> > > 
> > > To prevent such unwanted happening, we should restrict the
> > > plugins that can be specified by QT_IM_SWITCHER as real
> > > IM-switchers. It can be actualized by checking whether the
> > > specified plugin has the 'imsw-' prefix.
> > 
> > Above restriction is also implemented. See r67 of the
> > trunk. This restriction has changed the configuration convention
> > for system integrators as follows.
> > 
> > - valid configuration
> > 
> >   setenv QT_IM_SWITCHER imsw-none
> >   setenv QT_IM_MODULE iiimqcf
> > 
> > - following configuration has become invalid
> > 
> >   setenv QT_IM_SWITCHER iiimqcf
> 
> Sorry.  I have not noticed this description.
> I think it's better this restriction is bad.
> 
> IM-Switcher and IM-Module is same class.

Although technically same class for developers, psychologically
different class for users. This is why I had introduced the
restriction.

> So, it's better user can set IM-Module as IM-Switcher if user want.

I'm worrying about following situation. How do you think about it?

> > > It confuses ordinary users. Although ordinary users will not
> > > imagine such configuration, weird users will favor such
> > > configuration and publish their configuration memo to the
> > > world. It will confuse victims that googled with 'QT_IM_MODULE'.

-------------------------------
YamaKen  yamaken at bp.iij4u.or.jp