08:22orowith2os[m]: eugh
08:22orowith2os[m]: finally trying to map everything out
08:22orowith2os[m]: not quite sure what to do
08:22orowith2os[m]: go through the two protocols themselves and try and match them up as best I can?
08:23orowith2os[m]: go to the Wayland server-side API and map it to the X client side?
08:23orowith2os[m]: both?
08:23orowith2os[m]: what resources should I even use for X?
08:29orowith2os[m]: hm
08:29orowith2os[m]: well, I guess it's fine so long as Wayland clients have what they expect
08:29orowith2os[m]: so I can just focus on that area
09:05pq: orowith2os[m], you're correct, there is no concept of scale factor in X11 like there is in Wayland. The X11 premise is that pixels are shown 1:1 to any physical output pixel, and then clients "deal with it", without any need to tell anyone what they actually do.
09:06pq: orowith2os[m], OTOH, you might be able to use RandR to set a scaling matrix, but then that will not allow X11 clients to choose to render in high resolution directly as they would just all get scaled anyway again.
09:07orowith2os[m]: I'll leave that to later me or SDL to deal with
09:07pq: orowith2os[m], for X11 you have at least three bug pieces: X11 core protocol with all its extensions, and then the ICCCM and EWMH protocols built mostly on top of X11 window properties.
09:07pq: *big
09:07pq: a typo, I swear :-D
09:08orowith2os[m]: right now, I'm picking apart the wayland_server bits of wayland-rs so I can get a throwaway server going that I can then implement bits and pieces of the protocol for
09:08orowith2os[m]: whether that's done on top of a mix of SDL and X or bare X, I'll leave to the individuals involved later
09:09orowith2os[m]: and now I shall go bug the smithay folks :P
09:09pq: Do I understand right that you are aiming at running Wayland apps rootless on X11 server, or?
09:11orowith2os[m]: imagine something like weston running nested on X11, but more akin to Xwayland
09:11orowith2os[m]: in other words: a reverse-xwayland
09:11pq: right, exactly
09:12orowith2os[m]: I'm not sure how far I'll get, but I might as well try
09:12pq: I'd just go through the Wayland server-side interfaces and try to find how to do similar things on X11 using core protocol, extensions, ICCCM and EWMH.
09:13orowith2os[m]: I stayed up till 4AM, so it's a bit late to go to sleep in a reasonable timeframe, and don't really have anything better to do, soooo...
09:14pq: https://tronche.com/gui/x/ is the site I used for X11 basics
09:15orowith2os[m]: noted
09:15pq: looks like it includes ICCCM too
09:16pq: GWM I've never heard of
09:16MrCooper: orowith2os[m]: just in case you're not aware yet, X does not provide the atomicity guarantees required by Wayland, at least not without server grabs, which would likely suck in terms of user experience
09:16orowith2os[m]: ah, beautiful....
09:16pq: MrCooper, yeah, but since the host is X, who cares? :-)
09:17pq: at least visual glitching is totally accepted
09:17orowith2os[m]: and not supporting fractional and mixed scaling ;)
09:17MrCooper: to me that's one thing making that sort of thing pretty pointless, but to each their own :)
09:18orowith2os[m]: the main point of this project is to allow other projects to stop supporting X directly - they can just use Wayland, and work on Xorg as a result
09:18orowith2os[m]: (I'll deal with allowing access to the underlying X bits at some later point in time)
09:18pq: I guess EWMH is https://specifications.freedesktop.org/wm-spec/latest/
10:06immibis: orowith2os[m]: you might consider extending the X server to give it fractional scale maybe
10:06orowith2os[m]: nope nope nopeity nope
10:07orowith2os[m]: I am not touching that behemoth with a ten foot pole
10:09immibis: then don't do scaling at all
10:10orowith2os[m]: that's the plan, yep
10:10orowith2os[m]: or leave it to SDL to figure out
11:48kennylevinsen: immibis: the problem is not fractional scale in X, but no proper infrastructure for scale in X at all, and changing it is a no go as that would affect... Well everything.
13:17wlb: weston Merge request !1350 opened by Pekka Paalanen (pq) Unify initial monitor strings https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1350 [Core compositor], [DRM/KMS backend], [PipeWire plug-in], [Remoting plug-in]
13:24wlb: wayland Merge request !336 opened by Seunghun Lee (seunghun.shawn) client: fix segfault when removing uninitialized display->proxy.queue_link https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/336
13:51emersion: orowith2os[m]: yeah everything is optional
13:51emersion: for security-context
18:42wlb: wayland Issue #406 opened by Boud Roukema (broukema) Copy/paste popup does not appear when clicking menu button in squeekboard on foot or gnome-console https://gitlab.freedesktop.org/wayland/wayland/-/issues/406
21:42wlb: weston/main: Robert Mader * clients/simple-egl: Use interface name variables https://gitlab.freedesktop.org/wayland/weston/commit/d5753805b7da clients/simple-egl.c
21:42wlb: weston/main: Robert Mader * clients/simple-dmabuf-v4l: Use interface name variables https://gitlab.freedesktop.org/wayland/weston/commit/bf209e398511 clients/simple-dmabuf-v4l.c
21:42wlb: weston/main: Robert Mader * client/simple-dmabuf-v4l: Add fullscreen support https://gitlab.freedesktop.org/wayland/weston/commit/6cee95af3721 clients/ meson.build simple-dmabuf-v4l.c
21:42wlb: weston/main: Robert Mader * clients/simple-dmabuf-v4l: Add pointer support https://gitlab.freedesktop.org/wayland/weston/commit/68e2a606c056 clients/ meson.build simple-dmabuf-v4l.c
21:42wlb: weston Merge request !1345 merged \o/ (client/simple-dmabuf-v4l: Add fullscreen support https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1345)