Re: Handling of layout/input methods in Unity: what should we do for the LTS?

2013-11-16 Thread AWASHIRO Ikuya
Hi Sebastien, On Wed, 13 Nov 2013 16:04:14 +0100 Sebastien Bacher wrote: > Did we loose our indicator in the ibus 1.4->1.5 transition? We should > add it back in that's the case, yes This is the dropped patch. http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/ibus/saucy/revision/56#debi

Re: Handling of layout/input methods in Unity: what should we do for the LTS?

2013-11-13 Thread Loïc Minier
On Wed, Nov 13, 2013, Sebastien Bacher wrote: > That's a topic that should be discussed with the Mir/Unity8 though > ... do you know if that's on the roadmap for this cycle (handling of > external keyboards and layouts/input methods/keybindings on the > desktop)? (I don't know whether this is on t

Re: Handling of layout/input methods in Unity: what should we do for the LTS?

2013-11-13 Thread Sebastien Bacher
Le 13/11/2013 17:49, Loïc Minier a écrit : How will the Mir/Wayland approach look like? Could we leverage it for Unity 7? I expect the approach in "the new world" to be similar to the recent work. It should be easier under Mir/Wayland since we are not going to have to fight with X grabs and xk

Re: Handling of layout/input methods in Unity: what should we do for the LTS?

2013-11-13 Thread Loïc Minier
On Tue, Nov 12, 2013, Sebastien Bacher wrote: > * keep pushing forward to try to solve those issues (e.g move the > keygrabbing to compiz, look at where we stand there). > > That should give us a mostly working system, but: > - it means increasing changes before a LTS, which has potential to > cr

Re: Handling of layout/input methods in Unity: what should we do for the LTS?

2013-11-13 Thread Sebastien Bacher
Le 12/11/2013 17:55, Gunnar Hjalmarsson a écrit : Possibly a solution worth exploring for the Unity LTS. Hey Gunnar, Thanks for the suggestion. I would prefer avoiding trying a new solution though, especially during a LTS cycle. We have basically 2 options we experimented with, it would make

Re: Handling of layout/input methods in Unity: what should we do for the LTS?

2013-11-13 Thread Sebastien Bacher
Hi, Le 13/11/2013 13:40, AWASHIRO Ikuya a écrit : What does it mean? * Someone will write indicator patch for IBus 1.5. Did we loose our indicator in the ibus 1.4->1.5 transition? We should add it back in that's the case, yes * We use IBus embedded icon on Unity. * We switch back to IB

Re: Handling of layout/input methods in Unity: what should we do for the LTS?

2013-11-13 Thread AWASHIRO Ikuya
Hi Sebastien, On Tue, 12 Nov 2013 16:02:11 +0100 Sebastien Bacher wrote: > - we stop using our new keyboard indicator/get back to an UI which is > not what our design document recommend What does it mean? * Someone will write indicator patch for IBus 1.5. * We use IBus embedded icon on Unity.

Re: Handling of layout/input methods in Unity: what should we do for the LTS?

2013-11-12 Thread Gunnar Hjalmarsson
On 2013-11-12 16:02, Sebastien Bacher wrote: > * Since Ubuntu 13.10 > > - GNOME merged both concepts to provide an unified experience [1] Xubuntu 13.10 integrates keyboard layouts and input methods using IBus. Probably the GNOME changes haven't much to do with it; maybe IBus 1.5 has. Anyway,

Re: Handling of layout/input methods in Unity: what should we do for the LTS?

2013-11-12 Thread Sebastien Bacher
Le 12/11/2013 16:02, Sebastien Bacher a écrit : - it means basically adding back revert patches to gnome-settings-daemon/gnome-control-center, that's not really elegant but we had those until previous cycle and it was working Seems I forgot to add a note there ... we already have plans to hav

Handling of layout/input methods in Unity: what should we do for the LTS?

2013-11-12 Thread Sebastien Bacher
Hey everyone, I'm writing this email to get some input on how we should handle keyboard layouts/emails for the LTS. === Summary === In Ubuntu 13.10 we followed GNOME changes on how keyboard layouts and input methods are handle. Some of you probably noticed that things didn't go flawlessly t