<emersion>
(also added #dri-devel and #freedesktop while at it)
<daniels>
woot!
<pq>
sweet
<emersion>
hmm, irkerd isn't so great
<emersion>
it requires irkerd to be hidden behind a firewall in the same network as gitlab's
<emersion>
could always whitelist FDO IPs in my firewall, but it's a tad annoying if they're subject to change…
ivyl has joined #wayland
zamundaaa has joined #wayland
pnowack has joined #wayland
AbhijeetK has joined #wayland
bodiccea has joined #wayland
<daniels>
ah fun, no authentication
<emersion>
yeah :/
occivink has joined #wayland
FenTiger has joined #wayland
melissawen has quit [Quit: ZNC 1.7.2+deb3 - https://znc.in]
melissawen_ has joined #wayland
d_ed has joined #wayland
joes has joined #wayland
apol[m] has joined #wayland
<pq>
AbhijeetK, you also need to register and identify with nickserv to speak, because here too we suffer from spam. I mean, I haven't seen any message from you yet.
joes has quit []
<AbhijeetK>
Hi @pq
leandrohrb has joined #wayland
<pq>
AbhijeetK, heya
<AbhijeetK>
About deducing a fractional scale from `wl_output.mode/xdg_output.logical_size`, you suggested that a wayland compositor is allowed to do arbitrary, even non-linear transformations to the surface. Looking at isolated examples like that does not work.
<pq>
or maybe the monitor is just a plane in VR space
<pq>
observed via HMD
<pq>
or picture-in-picture on something else
<pq>
AbhijeetK, the wl_output transform is something else: it meant to allow direct scanout of client content.
<AbhijeetK>
Thanks @pq
<pq>
AbhijeetK, nothing in Wayland actually says that you cannot have a circular monitor with a pixel grid at a 40-degree angle, but Wayland does offer opportunities to take advantage of common cases where a more optimal hardware path is possible.
<pq>
wl_output interface is also one of the oldest things, and doesn't really live up to the modern Wayland ideas
<pq>
AbhijeetK, in general, one should not try to infer new things from old parameters that were never intended for it - like trying to guess the optimal buffer size from wl_output and xdg_output information.
melissawen_ has left #wayland [#wayland]
<pq>
If you need an optimal buffer size in a client, write a new protocol extension that delivers exactly that, with an explanation of what it actually means and what it is intended to be used for. Even doing that it will be hard to make everyone understand it the same way.
melissawen has joined #wayland
erc has joined #wayland
<AbhijeetK>
pq, Make sense. Thanks for the explanation. I was always thinking about a rectangular monitor display. I should read more about it. Can you suggest some resources?
<pq>
I don't know of any references.
<pq>
desktop-in-VR has been tried in a few places I think, and smart watches are a thing
<pq>
smart phones rarely have an exactly rectangular display either, there are rounded corners and carve-outs and curved-to-the-side displays
<pq>
on portable devices, one may also animate an orientation change - that is a temporary arbitrary image transformations which you probably wouldn't want to clients to keep up with during it.
occivink has quit [Quit: WeeChat 2.8]
occivink has joined #wayland
gitlab-bot has joined #wayland
bl4ckb0ne has joined #wayland
AbhijeetK has quit [Quit: Page closed]
blue__penquin has joined #wayland
occivink has quit [Quit: WeeChat 2.8]
occivink has joined #wayland
<pq>
whee, I got test_viewporter_double_create to be ASan-clean. \o/ ... aside from the leaks inside Cairo.
<pq>
that was a bit of a handful, since it uses desktop-shell, which spawns weston-desktop-shell and weston-keyboard and they all needed fixing, and toytoolkit.