On Mon, Sep 11, 2017 at 3:44 PM, Adam Jackson wrote:
> On Sun, 2017-09-10 at 22:25 +0200, Joseph Burt wrote:
>
>> What about always running the X server at hardware resolution,
>
> This isn't a fixed number. Outputs can be hotplugged.
Oh yeah, and they can have di
On Fri, Sep 8, 2017 at 11:02 AM, Pekka Paalanen wrote:
> On Thu, 7 Sep 2017 21:18:48 +0200
> Joseph Burt wrote:
>
>> Hi all,
>>
>> On Wed, Sep 6, 2017 at 1:09 PM, Daniel Stone wrote:
>> >
>> > I really wouldn't recommend doing this.
>>
&
On Mon, Sep 11, 2017 at 9:08 AM, Olivier Fourdan wrote:
> Hi
>
> On 10 September 2017 at 22:25, Joseph Burt wrote:
>>
>>
>> I'm now up to date on the relevant bug reports. Sorry for the spam.
>>
>> What about always running the X server at hardwa
On Sun, Sep 10, 2017 at 5:01 PM, Joseph Burt wrote:
> Hi Olivier,
>
> On Thu, Sep 7, 2017 at 6:17 PM, Olivier Fourdan wrote:
>>
>> The other solution would be to have the same screen, but have Xwayland to
>> give different scaling conversions for root windo
Hi Olivier,
On Thu, Sep 7, 2017 at 6:17 PM, Olivier Fourdan wrote:
>
> The other solution would be to have the same screen, but have Xwayland to
> give different scaling conversions for root window size, screen size, events
> coordinates, etc. depending on the client, if it's HiDPI aware or not,
Hi all,
On Wed, Sep 6, 2017 at 1:09 PM, Daniel Stone wrote:
>
> I really wouldn't recommend doing this.
On Thu, Sep 7, 2017 at 10:05 AM, Pekka Paalanen wrote:
>
> I kind of wish I shared your optimism, but I'm thinking more of a death
> by a thousand papercuts kind of situation, not a single bi
On Thu, Sep 7, 2017 at 9:43 AM, Carsten Haitzler wrote:
> It doesn't have to be specified in the protocol. It is what every compositor
> does because everyone agreed early on that CSD is the default. Weston did it
> then everyone else did it. To be compatible everyone stayed the same. They
> have
On Thu, Sep 7, 2017 at 1:17 AM, Carsten Haitzler wrote:
>
> It is CSD in Wayland for Wayland clients, unless somehow compositor and client
> negotiate something else. In the default case, if a client does not decorate
> it
> will not get any decorations (titlebar and so on) at all.
IIRC that's n
On Wed, Sep 6, 2017 at 4:45 PM, Pekka Paalanen wrote:
> Popups (e.g. menus) in Wayland use protocol that provides the server
> with:
> - the relationship to the window which the popup is for, and
> - the input event identity that triggered the popup.
>
> These are required on Wayland: the parent w
Hi Daniel,
On Wed, Sep 6, 2017 at 1:09 PM, Daniel Stone wrote:
>
> No-one wanted to write yet another X11 window manager; what's there is
> there by necessity so as not to break existing clients. For instance,
> pop-up menus rely heavily on the global co-ordinate system remaining
> intact.
Are p
Hi Olivier,
On Wed, Sep 6, 2017 at 1:05 PM, Olivier Fourdan wrote:
>
> One thing to consider as well is that you will need to decorate the X11
> windows as Wayland is basically client side decorations.
I was under the impression that Wayland doesn't specify client- or
server-side decoration, and
Fourdan wrote:
>
>> Hi,
>>
>> On 6 September 2017 at 11:48, Joseph Burt wrote:
>>
>> > To be clear, my first look at how the X11 channel is used in practice
>> > hasn't yet turned up the justification for its existence. The logic
>> >
hannel is a big protocol extension, but I haven't found any
discussion of that design decision. Can anyone point me in the right
direction?
Thanks,
Joseph
On Tue, Sep 5, 2017 at 7:51 PM, Joseph Burt wrote:
> Most Wayland compositors, Weston and WLC-based ones included, carry
>
w manager in the Wayland compositor.
>
> Cheers,
> Olivier
>
>
> On 5 September 2017 at 19:51, Joseph Burt wrote:
>>
>> Most Wayland compositors, Weston and WLC-based ones included, carry
>> around a bit of XWM code, essentially a protocol extension, to deal
>
Most Wayland compositors, Weston and WLC-based ones included, carry
around a bit of XWM code, essentially a protocol extension, to deal
with Xwayland. Why? What is lacking in Xwayland?
Thanks,
Joseph
___
wayland-devel mailing list
wayland-devel@lists.fre
15 matches
Mail list logo
