Bug 78372 - create multiple windows with offset

[Jasper St. Pierre]

On Thu, May 8, 2014 at 4:13 PM, Bill Spitzak <spitzak at gmail.com> wrote:

> On 05/08/2014 11:31 AM, Jasper St. Pierre wrote:
>
>> I don't know how you can have been on the Wayland mailing list for this
>> long and not grasp core Wayland protocol concepts. Clients cannot get
>> global surface positions, and it's been that way since day 1 six years
>> ago.
>>
>
> Yes I know that. I said EXACTLY that in my email:
>
>
> >     As any such x/y position has been explicitly stated as being
> >     disallowed by Wayland...
>
> Maybe my email is hard to read. I have a SIMPLE question:
>
> "Can you supply a vague idea on how you imagine a client can control it's
> window layout without adding an x/y position to the api."
>

Clients should simply not attempt their window layout. There's a lot of
issues, like hotpluggable outputs, that make it difficult for a client to
do.


> Unless there is an answer to this question I see no reason to make a
> feature request that, as far as I can tell, is impossible to fulfill.
>
>
>  I also have never seen a patch or a line of code from you, ever.
>>
>
> I posted the same patch for the xserver for 6 months to allow it to read a
> different xorg.conf file. I finally got sick of being ignored and gave up,
> also recent xwayland can now work on a non-EGL wayland without having a
> special xorg.conf file, thus "fixing" it for me. However the underlying bug
> still exists and I'm sure there will be text that has to be in one
> xorg.conf file or the other that makes the other server choke. Maybe then
> somebody will fix it.
>

xorg.conf is outdated, and really shouldn't be used in production. It's
been replaced by /etc/xorg.conf.d. Xwayland shouldn't require *any*
configuration. At all. If we need to configure Xwayland somewhere, we've
messed up. If you're still having issues getting Xwayland up and running,
you can email the list for support, or ask on the IRC channel.

Keep in mind that `Xorg -config` and `Xorg -configdir` have existed for
some time now, so I'm not exactly sure what your patch did.

I would love to work on Wayland, but until I can be confident that I am
> compiling and running it correctly there is little I can do. I have posted
> questions about whether anybody else is seeing the rendering errors in X
> clients, and whether EGL clients should work on a non-EGL backend, but have
> not gotten any response, despite the fact that I am only interested in
> trivial yes/no answers.
>

I haven't seen any rendering errors in X clients, but there's a lot of
variables there. More feedback on what you're seeing, with what drivers,
and on what hardware would be appreciated.

EGL clients can theoretically work on a non-EGL backend for certain cases
where we can poke under the hood of the FOSS stack, but neither Weston nor
mutter do that.

-- 
  Jasper
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-devel/attachments/20140508/960b79f6/attachment.html>