Is Wayland without X11 matured
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:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Is Wayland without X11 matured
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's maturing very quickly, but there are still issues here and there. On Wed, Mar 19, 2014 at 6:52 AM, Sathish Kumar Balasubramaniam -ERS, HCL Tech b-sathishku...@hcl.com wrote: 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:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel -- Jasper ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: [PATCH 0/3] Add wl_output name event
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 quanxian.w...@intel.comwrote: This event contains a human-readable name of output. It may be sent after binding the output object. It is intended that the client can use this output name as a parameter or display it in logs. For example, in weston randr application, output name can be a parameter in command line to stand for an output. Quanxian Wang (3): wayland: Add wl_output name event shell: Add wl_output name event weston:Add wl_output name event Wayland: protocol/wayland.xml | 12 +++- 1 file changed, 11 insertions(+), 1 deletion(-) Shell: clients/desktop-shell.c | 12 ++-- clients/window.c| 12 ++-- 2 files changed, 20 insertions(+), 4 deletions(-) Weston: src/compositor.c| 7 +-- 1 files changed, 5 insertions(+), 2 deletions(-) -- 1.8.1.2 ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Is Wayland without X11 matured
Hi, On 19 March 2014 13:18, Jasper St. Pierre jstpie...@mecheye.net 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 reinvent on Wayland. Depends how you define complexity. :) In this case, I guess you mean complexity in the shell / user-facing window management / user interaction case. You can construct quite complex usecases that don't place such heavy and complex demands on window management just fine; for example, it's being shipped in cars, set-top boxes, etc. These are all quite complex, but don't have those desktop shell requirements around window management. Cheers, Daniel We're working on them all the time, so it's maturing very quickly, but there are still issues here and there. On Wed, Mar 19, 2014 at 6:52 AM, Sathish Kumar Balasubramaniam -ERS, HCL Tech b-sathishku...@hcl.com wrote: 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:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel -- Jasper ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
RE: [PATCH 0/3] Add wl_output name event
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 from a technical perspective. I'm still not 100% sure that this is needed, but I think I'm ok with it. --Jason Ekstrand [Wang, Quanxian] That is fine. Thanks On Wed, Mar 19, 2014 at 12:30 AM, Quanxian Wang quanxian.w...@intel.commailto:quanxian.w...@intel.com wrote: This event contains a human-readable name of output. It may be sent after binding the output object. It is intended that the client can use this output name as a parameter or display it in logs. For example, in weston randr application, output name can be a parameter in command line to stand for an output. Quanxian Wang (3): wayland: Add wl_output name event shell: Add wl_output name event weston:Add wl_output name event Wayland: protocol/wayland.xml | 12 +++- 1 file changed, 11 insertions(+), 1 deletion(-) Shell: clients/desktop-shell.c | 12 ++-- clients/window.c| 12 ++-- 2 files changed, 20 insertions(+), 4 deletions(-) Weston: src/compositor.c| 7 +-- 1 files changed, 5 insertions(+), 2 deletions(-) -- 1.8.1.2 ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
RE: Is Wayland without X11 matured
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 Subject: Re: Is Wayland without X11 matured Hi, On 19 March 2014 13:18, Jasper St. Pierre jstpie...@mecheye.net 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 reinvent on Wayland. Depends how you define complexity. :) In this case, I guess you mean complexity in the shell / user-facing window management / user interaction case. You can construct quite complex usecases that don't place such heavy and complex demands on window management just fine; for example, it's being shipped in cars, set-top boxes, etc. These are all quite complex, but don't have those desktop shell requirements around window management. Cheers, Daniel We're working on them all the time, so it's maturing very quickly, but there are still issues here and there. On Wed, Mar 19, 2014 at 6:52 AM, Sathish Kumar Balasubramaniam -ERS, HCL Tech b-sathishku...@hcl.com wrote: 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:: - - -- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. - - -- ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel -- Jasper ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
