Hey,
I've been looking at the new ibus/g-s-d/g-c-c stack recently to update
in raring and I'm not convinced it's a good idea to update to those. We
have discussed the issue a bit on IRC today but I figured I would write
an email to the list to document and share the thinking.
There seem to b
On Tue, Nov 20, 2012 at 12:13 PM, Sebastien Bacher wrote:
> I've been looking at the new ibus/g-s-d/g-c-c stack recently to update in
> raring and I'm not convinced it's a good idea to update to those. We have
> discussed the issue a bit on IRC today but I figured I would write an email
> to the l
On 20 November 2012 15:31, Ma Xiaojun wrote:
> On Tue, Nov 20, 2012 at 12:13 PM, Sebastien Bacher wrote:
>> I've been looking at the new ibus/g-s-d/g-c-c stack recently to update in
>> raring and I'm not convinced it's a good idea to update to those. We have
>> discussed the issue a bit on IRC to
On Tue, Nov 20, 2012 at 3:06 PM, Jeremy Bicha wrote:
> http://irclogs.ubuntu.com/2012/11/20/%23ubuntu-desktop.html#t14:59 until 16:30
OK, I will try to stay there since now, not to miss such discussions.
> https://blueprints.launchpad.net/ubuntu/+spec/desktop-r-gnome-fallback
>
> I don't think w
On 21/11/12 07:13, Sebastien Bacher wrote:
> Hey,
>
> I've been looking at the new ibus/g-s-d/g-c-c stack recently to update
> in raring and I'm not convinced it's a good idea to update to those.
> We have discussed the issue a bit on IRC today but I figured I would
> write an email to the list to
On 20 November 2012 16:59, Ma Xiaojun wrote:
>> https://blueprints.launchpad.net/ubuntu/+spec/desktop-r-gnome-fallback
>>
>> I don't think work on porting the indicator patch to ibus 1.4.99 has
>> really started yet. Seb was looking at it, which sparked this
>> discussion.
>
> You need to be clear
Sorry for not repeating the list previously, jbicha.
On Tue, Nov 20, 2012 at 4:29 PM, Jeremy Bicha wrote:
> I believe the design plan was basically that the indicator should "do
> like what it did in Quantal…unless we can do it better".
I repeat, current IBus indicator isn't working right becaus
Hi,
On Tue, 20 Nov 2012 19:13:10 +0100
Sebastien Bacher wrote:
> Our options, if we stay on the current ibus, are:
> - stay on g-s-d/g-c-c 3.4 (the current version)
> - update g-s-d/g-c-c to 3.6 fully using the upstream code without
> building with ibus (they have a fallback mode without ibus i
On Tue, Nov 20, 2012 at 9:47 PM, AWASHIRO Ikuya wrote:
> $ sudo add-apt-repository ppa:jbicha/ibus
> $ sudo apt-get update;sudo apt-get upgrade
> $ gsettings set com.canonical.Unity.Panel systray-whitelist
> "['JavaEmbeddedFrame', 'Wine', 'Update-notifier', 'ibus']"
> $ gsettings set org.gnome.se
On Tue, 20 Nov 2012 23:55:56 -0600
Ma Xiaojun wrote:
> You are not concerned with the global state issue?
I don't understand what is the problem well, IBus 1.4.99.20121006 still
have Global input method settings.
Thanks,
--
AWASHIRO Ikuya
ik...@fruitsbasket.info / ik...@oooug.jp / iku...@gmail.
On Wed, Nov 21, 2012 at 12:20 AM, AWASHIRO Ikuya wrote:
> I don't understand what is the problem well, IBus 1.4.99.20121006 still
> have Global input method settings.
The problem is that it enforces global input source state now.
In 1.4 it is configurable, you can have either local (per window /
On Wed, 21 Nov 2012 01:44:58 -0600
Ma Xiaojun wrote:
> The problem is that it enforces global input source state now.
> In 1.4 it is configurable, you can have either local (per window /
> input context) or global state.
> I received issue report June this year for this.
> http://code.google.com/
Le 20/11/2012 21:31, Ma Xiaojun a écrit :
Exactly.
I probably want to try adding such feature back to IBus itself at certain point.
But I have no confidence of persuading so-called GNOME design people,
please help.
Do you have a list of the features that are missing in the 1.5 update?
Is that m
On Wed, Nov 21, 2012 at 4:47 AM, Sebastien Bacher wrote:
> Do you have a list of the features that are missing in the 1.5 update? Is
> that mostly the "input method per win" option? I will try to resume/continue
> the GNOME upstream discussion on the topic
Yes, mostly the "input method per win" o
On 20 November 2012 13:13, Sebastien Bacher wrote:
> I've been looking at the new ibus/g-s-d/g-c-c stack recently to update in
> raring and I'm not convinced it's a good idea to update to those. We have
> discussed the issue a bit on IRC today but I figured I would write an email
> to the list to
On Sat, Jun 8, 2013 at 8:47 AM, Jeremy Bicha wrote:
> Hey could we revisit this topic and see what still is blocking ibus
> 1.5 from Ubuntu?
Sure.
> The 'separate input sources per window' feature has apparently
> returned which was a big blocker last year.[1]
Well, it is returned in GNOME Shel
After GNOME people decided that per windows input source (layout or
input method) is useless.
https://bugzilla.gnome.org/show_bug.cgi?id=684210
( The feature existed in 3.4 and before)
They made something even more surprising; white listing input engines
and properties input engines can expose.
S
On 23 November 2012 18:49, Ma Xiaojun wrote:
> They made something even more surprising; white listing input engines
> and properties input engines can expose.
>
> The first one does affect us, though a patch would be easy to write.
> We have decent packages for every working IBus engines in our
>
On Fri, Nov 23, 2012 at 6:40 PM, Jeremy Bicha wrote:
> It's very easy for Ubuntu as a distro to change a gsettings default
> (that's what ubuntu-settings and ubuntu-gnome-default-settings do).
Well, show_all_source won't be a good option since it would show some
useless engines either. The only t
19 matches
Mail list logo
