On Fri, Mar 11, 2016 at 03:46:21PM +1000, Peter Hutterer wrote: > On Thu, Mar 10, 2016 at 01:43:13PM -0500, Matthias Clasen wrote: > > Anyway, I'd like to hear people's thoughts about this topic. > > fwiw, I fully agree that this need to be implemented on the compositor side. > Client-side first is a nice principle for things that are client-specific > but I see accessibility as a feature of the user, not of the software. Thus > it falls into the same category as other user-specific features like tapping > that are already implemented in the compositor (or even hidden inside > libinput).
Along this line of thinking, I notice that weston-simple-im.c implements compose sequences, but should compose key be client-side or might it fit in with something like this on the compositor side? I'm a bit confused how compose key support is intended to work in Weston. Bryce _______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
