Re: Concerning Keyboard Status Menu

[Bastien Nocera <hadess hadess net>]

On Thu, 2012-11-22 at 23:58 -0600, Ma Xiaojun wrote:
> On Thu, Nov 22, 2012 at 11:54 PM, anish patil <anish developer gmail com> wrote:
> 
> > Such a mail thread is limitless, we need to think about working solutions or
> > solving the problems
> > How about creating a wiki page about current problems? what you expect from
> > GNOME upstream/designers ? What you expect from Ibus?
> 
> Engine list filtering should be changed to black list instead.
> I guess we need to black list some m17n advertised engines and ibus-xkbc.
> The code change should be easy but determining black list need some
> effort, I'm trying now.
> 
> Property menu filtering should be removed, I'd do this before above task.

Do you realise you've still not given a single good reason why we should
do that? You gave 2 reasons to do that:
- to enable users to use newly installed engines, for which we don't
need to remove filtering
- Because users want to see a long list of half-broken, unmaintained
engines that they wouldn't know which one to choose for their language

You filed a bug in the middle of this conversation:
https://bugzilla.gnome.org/show_bug.cgi?id=688914

With gems like:
> http://code.google.com/p/ibus-cloud-pinyin/
> ( This one is outdated, it will may revive though. )
> http://code.google.com/p/ibus-t9/
> ( I'm not sure about the current state of this one. )

You just listed 2 good reasons to keep a whitelist.

I filed a bug about letting users select newly installed engines, which
makes sense, but it's likely going to be invasive and for 3.8 only:
https://bugzilla.gnome.org/show_bug.cgi?id=688918

So you'd be better get started on proposing missing engines for the
languages you care about and know.