On 2018-05-15 3:01 PM, Olivier Fourdan wrote:
> FWIW, both SDL and Xwayland uses “persistent” and we have working
> implementations of the protocol in weston/libweston and mutter, so it might
> be hard to convince people (both compositor and clients developers) to drop
> their working implementati
Hi Drew,
On 17 May 2018 at 13:11, Drew DeVault wrote:
> On 2018-05-15 3:01 PM, Olivier Fourdan wrote:
>> FWIW, both SDL and Xwayland uses “persistent” and we have working
>> implementations of the protocol in weston/libweston and mutter, so it might
>> be hard to convince people (both compositor
On 2018-05-17 1:14 PM, Daniel Stone wrote:
> That's fine, but we would have to look at the trade-off: they would
> have to drop functionality they use, in exchange for something which
> is worse for them.
I guess I don't fully understand why it's worse for them. It should be
functionally equivale
On Wed, 16 May 2018 06:41:08 +
Sandeep Chandak wrote:
> Hi,
>
> We are using Weston Wayland based compositing for our solution,
> though we are able to render image, video text etc.
>
> We are using x11 backend along with desktop shell to build the
> solution which requires rendering of mul
Provides the ability to emulate keyboards by applications. Complementary to
input-method protocol.
The interface is a mirror copy of wl_keyboard, with removed serials, and added
seat binding.
---
This proposal is another one needed by Purism to support on screen keyboards on
a phone screen.
V
Hi Dorota,
On 3 May 2018 at 16:41, Dorota Czaplejewicz wrote:
> - There is no event to send keysyms. Compositors can use wl_keyboard
> interface instead.
The reason we explicitly chose to have a keysym (really, 'Unicode
codepoint') event, is to support characters which don't appear in any
keym
On Thu, 17 May 2018 18:05:34 +0100
Daniel Stone wrote:
> Hi Dorota,
>
> On 3 May 2018 at 16:41, Dorota Czaplejewicz
> wrote:
> > - There is no event to send keysyms. Compositors can use wl_keyboard
> > interface instead.
>
> The reason we explicitly chose to have a keysym (really, 'Unicod
Hi Peter,
I see your point that there would still need to exist vendor-specific code. My
point is that reading that vendor-specific data would be responsibility of the
end-user (the people making a wayland client), instead of """polluting""" the
protocol with vendor-specific details. But, if th
Oh, the ID is unique for all type of objects! That works :)
Thanks,
Felipe
‐‐‐ Original Message ‐‐‐
On May 14, 2018 5:38 AM, Pekka Paalanen wrote:
> On Sat, 12 May 2018 06:34:36 -0400
>
> ferreiradaselva ferreiradase...@protonmail.com wrote:
>
> > Hi,
> >
> > Excuse me if this is
On Thu, May 17, 2018 at 05:25:26PM -0400, ferreiradaselva wrote:
> Hi Peter,
>
> I see your point that there would still need to exist vendor-specific
> code. My point is that reading that vendor-specific data would be
> responsibility of the end-user (the people making a wayland client),
> instea
10 matches
Mail list logo