ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput | register your nick to speak
caveman has quit [Remote host closed the connection]
caveman has joined #wayland
hardening has quit [Ping timeout: 480 seconds]
maxzor has quit [Remote host closed the connection]
maxzor has joined #wayland
maxzor has quit [Remote host closed the connection]
maxzor has joined #wayland
maxzor has quit [Remote host closed the connection]
maxzor has joined #wayland
maxzor has quit [Remote host closed the connection]
maxzor has joined #wayland
maxzor has quit [Remote host closed the connection]
maxzor has joined #wayland
sozuba has joined #wayland
maxzor has quit [Remote host closed the connection]
maxzor has joined #wayland
Leopold_ has quit [Remote host closed the connection]
Leopold_ has joined #wayland
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
nerdopolis has quit []
nerdopolis has joined #wayland
maxzor has quit [Ping timeout: 480 seconds]
maxzor has joined #wayland
maxzor_ has joined #wayland
maxzor has quit [Ping timeout: 480 seconds]
ybogdano has quit [Ping timeout: 480 seconds]
sozuba has quit [Ping timeout: 480 seconds]
nerdopolis has quit [Ping timeout: 480 seconds]
maxzor_ has quit [Remote host closed the connection]
maxzor_ has joined #wayland
maxzor__ has joined #wayland
maxzor_ has quit [Ping timeout: 480 seconds]
caveman has quit [Remote host closed the connection]
caveman has joined #wayland
maxzor__ has quit [Remote host closed the connection]
maxzor__ has joined #wayland
maxzor__ has quit [Remote host closed the connection]
<yshui`>
pq, then i feel it has the same problem as scale. a) it is 1 frame too late. b) the compositor might not want the client to pre-rotate, like when it's not possible to direct scan out
<pq>
yshui`, you are corrent, and the MR we talked about fixes that too.
<pq>
*correct
<yshui`>
ah nice! i thought it was only about scale ^^;
<pq>
originally it was, but I think transform was added
junaid has joined #wayland
<yshui`>
nice
maxzor__ has quit [Remote host closed the connection]
maxzor__ has joined #wayland
junaid has quit [Ping timeout: 480 seconds]
maxzor__ has quit [Remote host closed the connection]
maxzor__ has joined #wayland
<wlb>
weston Merge request !1076 opened by Pekka Paalanen (pq) Refactor and share the output decorations GL-renderer setup code between headless and wayland backends https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1076 [Headless backend], [Nested Wayland backend]
andrea has joined #wayland
andrea has quit []
andrea has joined #wayland
andrea is now known as Guest1475
Guest1475 has quit []
andrea_ has joined #wayland
maxzor__ has quit [Remote host closed the connection]
maxzor__ has joined #wayland
andrea_ has quit []
maxzor__ has quit [Remote host closed the connection]
maxzor__ has joined #wayland
fmuellner has joined #wayland
junaid has joined #wayland
Paul33 has quit []
Paul33 has joined #wayland
MajorBiscuit has quit [Ping timeout: 480 seconds]
qaqland[m] has joined #wayland
sozuba has joined #wayland
MajorBiscuit has joined #wayland
kts has quit [Quit: Leaving]
sozuba has quit [Ping timeout: 480 seconds]
junaid has quit [Quit: leaving]
junaid has joined #wayland
Lucretia-backup has quit []
Lucretia has joined #wayland
sozuba has joined #wayland
devilhorns has quit []
MajorBiscuit has quit [Quit: WeeChat 3.6]
<pq>
What (GUI) client toolkit would you recommend for a Rust program that needs to access custom Wayland extensions? Something that comes or can be used with a GUI widget library.
<bl4ckb0ne>
i dont think such thing exist, client toolkits are always very abstract
<pq>
yeah, so I've started to see
junaid has quit [Remote host closed the connection]
<pq>
but I'd want to use ready-made widgets on a custom wl_surface role.
<davidre>
In Qt we ahve QWaylandClientExtension which automatically bind to a global
<bl4ckb0ne>
i have somewhat of a start of one in C
<pq>
my main goal is to keep up with Rust while doing something interesting (Wayland/Weston related), IOW see how hard it would be to write a weston-desktop-shell helper client replacement in Rust.
<pq>
at least there seems to be a Rust crate for abstract display and window "raw" handles, which gives hope that one could maybe use an existingin widget library with a custom wl_surface.
junaid has joined #wayland
junaid has quit [Remote host closed the connection]
floof58 is now known as Guest1495
floof58 has joined #wayland
Guest1495 has quit [Ping timeout: 480 seconds]
<i509VCB>
We've had people pop around in the wayland-rs matrix asking about that, we did make a split between the general API exposed to Rust and the lower level protocol API so such experiments could be easier. I recall a few people tried but I can't recall any links off head
jgrulich has quit [Remote host closed the connection]