Thanks, Jasper and Daniel.
I was asking it from an IVI perspective.
-Original Message-
From: Daniel Stone [mailto:dan...@fooishbar.org]
Sent: Thursday, March 20, 2014 12:01 AM
To: Jasper St. Pierre
Cc: Sathish Kumar Balasubramaniam -ERS, HCL Tech;
wayland-devel@lists.freedesktop.org
Su
From: Jason Ekstrand [mailto:ja...@jlekstrand.net]
Sent: Thursday, March 20, 2014 1:02 AM
To: Wang, Quanxian
Cc: wayland-devel@lists.freedesktop.org; Bryce Harrington
Subject: Re: [PATCH 0/3] Add wl_output name event
Quaxian,
I looked over the latest versions, and I think they all look good now
Hi,
On 19 March 2014 13:18, Jasper St. Pierre wrote:
> For very simple use cases, it's fairly mature. You can use it on embedded
> systems quite well.
>
> For complex desktops, it's not quite. There's a lot of protocols that are
> traditionally in something like the ICCCM or EWMH that we have to
Quaxian,
I looked over the latest versions, and I think they all look good now from
a technical perspective. I'm still not 100% sure that this is needed, but
I think I'm ok with it.
--Jason Ekstrand
On Wed, Mar 19, 2014 at 12:30 AM, Quanxian Wang wrote:
> This event contains a human-readable na
For very simple use cases, it's fairly mature. You can use it on embedded
systems quite well.
For complex desktops, it's not quite. There's a lot of protocols that are
traditionally in something like the ICCCM or EWMH that we have to reinvent
on Wayland.
We're working on them all the time, so it'
Hi,
I would like to know, for 2D and 3D apps, using Wayland without X11 is matured
and successful or still it needs to get matured ?
Regards,
B.Sathish Kumar
::DISCLAIMER::
-
On Mon, Mar 17, 2014 at 02:52:11PM -0400, Stephen Chandler Paul wrote:
> Hello,
> I'm a college student who is looking into taking part in the Google
> Summer of Code, specifically with X.Org and Wayland. However, I've been
> having a bit of a challenge finding a project proposal that I think
On Wed, 19 Mar 2014 00:21:20 +0100
Hardening wrote:
> Le 18/03/2014 20:34, Bryce W. Harrington a écrit :
> > weston_log() seems to be the standard elsewhere in the codebase for
> > errors. These are the only two instances where perror() is used
> > instead, and their error messages aren't that i