Re: Concerning Keyboard Status Menu

2012-11-23 Thread Caius Chance
Hi all,

I would think GNOME as OSS should treat everything open without
discriminating any input method platform or input method engines. Every
person has different value on quality, which creating a white/blacklist to
separate engines based on some criteria defined by a board is appropriate.

Input methods and keyboard layouts is NOT similar in any bit. Most of the
keyboard layouts are 1 to 1 key-char mapping but input method is superset
to that. I hope anyone who believes that check out the Cangjie input
method, since you need substantial (its a subjective word just as
low-quality mentioned in previous comments) information for you to defend
the whitelist approach.

I am against any filtering in input method / input method engine because
talking about user friendly or usability of GNOME to other high quality
environment, it should be beyond the whiltelist by public, too. I
personally urge GNOME devs leave the decision rights to IBus itself and its
engines, or just join the IBus development and work right on it instead of
hacking from GNOME.

Regards,
kaio


On 23 November 2012 22:15, Justin Wong bigea...@xdlinux.info wrote:

 I should say fcitx with kimpanel still works at gnome 3.6 , but it's
  running slower than that in gnome 3.4, and  even slower than that in gnome
 3.2, which means a same extension is running slower and slower with
 gnome-shell upgrades.

 As ibus experience still sucks at gnome, ibus or gnome, which one would u
 drop?
 Yuanfang, what do you say?


 On Fri, Nov 23, 2012 at 7:17 PM, Ma Xiaojun damage3...@gmail.com wrote:

 To make my point clear.

 Once we have a fixed framework of inputting.
 Installing/Uninstalling a new engine should be similar to
 installing/uninstalling a new app.
 There is no black magic here.
 ___
 desktop-devel-list mailing list
 desktop-devel-list@gnome.org
 https://mail.gnome.org/mailman/listinfo/desktop-devel-list




 --
 Open Source,Open Mind

 Blog:http://bigeagle.me/
 E-mail:  bigea...@xdlinux.info

 ___
 desktop-devel-list mailing list
 desktop-devel-list@gnome.org
 https://mail.gnome.org/mailman/listinfo/desktop-devel-list

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Concerning Keyboard Status Menu

2012-11-23 Thread Caius Chance
s/appropriate/inappropriate/


On 24 November 2012 00:04, Caius Chance m...@kaio.net wrote:

 Hi all,

 I would think GNOME as OSS should treat everything open without
 discriminating any input method platform or input method engines. Every
 person has different value on quality, which creating a white/blacklist to
 separate engines based on some criteria defined by a board is appropriate.

 Input methods and keyboard layouts is NOT similar in any bit. Most of the
 keyboard layouts are 1 to 1 key-char mapping but input method is superset
 to that. I hope anyone who believes that check out the Cangjie input
 method, since you need substantial (its a subjective word just as
 low-quality mentioned in previous comments) information for you to defend
 the whitelist approach.

 I am against any filtering in input method / input method engine because
 talking about user friendly or usability of GNOME to other high quality
 environment, it should be beyond the whiltelist by public, too. I
 personally urge GNOME devs leave the decision rights to IBus itself and its
 engines, or just join the IBus development and work right on it instead of
 hacking from GNOME.

 Regards,
 kaio


 On 23 November 2012 22:15, Justin Wong bigea...@xdlinux.info wrote:

 I should say fcitx with kimpanel still works at gnome 3.6 , but it's
  running slower than that in gnome 3.4, and  even slower than that in gnome
 3.2, which means a same extension is running slower and slower with
 gnome-shell upgrades.

 As ibus experience still sucks at gnome, ibus or gnome, which one would u
 drop?
 Yuanfang, what do you say?


 On Fri, Nov 23, 2012 at 7:17 PM, Ma Xiaojun damage3...@gmail.com wrote:

 To make my point clear.

 Once we have a fixed framework of inputting.
 Installing/Uninstalling a new engine should be similar to
 installing/uninstalling a new app.
 There is no black magic here.
 ___
 desktop-devel-list mailing list
 desktop-devel-list@gnome.org
 https://mail.gnome.org/mailman/listinfo/desktop-devel-list




 --
 Open Source,Open Mind

 Blog:http://bigeagle.me/
 E-mail:  bigea...@xdlinux.info

 ___
 desktop-devel-list mailing list
 desktop-devel-list@gnome.org
 https://mail.gnome.org/mailman/listinfo/desktop-devel-list



___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list