Live data from Hacker News

State of multi-player Wayland

blinry.org

111–115 of 115 posts

Re: State of multi-player Wayland

#111

I have never liked split keyboards but I might if each keyboard was also a mouse with its own cursor, it seems fun to develop the skill to work that way. Would also be useful at times if the the Thinkpad trackpoint and trackpad could each have their own cursor and I could leave one somewhere. Or maybe a cursor stack like pushd/popd, registers would probably work better; instead of virtual desktops just give me one ma…

Wayland seats are sets of inputs, to be handled together, each seat having its own cursor position, focused element, and so forth. That’s not what you want, I believe. … unless you do want the left half of your keyboard to type into one window, and the right half of your keyboard into another.

[deleted]

Re: State of multi-player Wayland

#112

To add to the long list of caveats: This also breaks assumptions GUI toolkit and applications make about only one of their windows being focused at a time: `gtk_application_get_active_window`, `QApplication::activeWindow`, etc.

[deleted]

Re: State of multi-player Wayland

#113
post #89
post #8

I'm building a compositor now, and I've been thinking about multi-seat from the beginning, but I know there are lots of places that assume a single seat, and so this sort of thing won't work for me. It's actually a lot more work than you'd think to support this...

One very nice use case that I haven't seen anyone else talk about is touchscreens. I have assigned my touchscreen to be in a separate seat. This allows me to interact with apps without moving my cursor or changing my window focus. For instance: web browser on the left, with a document. Text editor on the right. I am writing some notes with my keyboard, scrolling the document with my touchscreen. The editor stays focu…

Also, large touchscreens can be really nice for collaboration, with multiple users interacting with one or multiple apps at the same time.

Re: State of multi-player Wayland

#114
post #92

> This is obviously not a great solution, and VNC in general feels like ancient technology It's not obvious to me. This looks like software ageism. :) There are at least 2 things that could be done to improve performance in the author's setup: 1. Use the --gpu flag which enables dmabuf capture and h264 encoding via vaapi. 2. Connect using a dedicated VNC client like TigerVNC. This reduces latency by roughly 50 ms. Fo…

Well software has gradually improved and VNC hasn't so of course it's "software ageism". In any case if you were seriously not aware of VNC's shortcomings compared to modern alternatives: 1. Hilarious security. Passwords silently truncated to 8 characters, etc. 2. Inefficient graphics. Very laggy on all but the best connections. Just sending an H.264 video stream is better these days. 3. No seamless window mode. 4. I…

re #2 see metavnc (old at this point)

https://metavnc.sourceforge.net/

TLDR: it leveraged a specific client that could

a) connect to multiple vnc instances b) display them in a single window c) act as the "window manager" / "desktop environment" - doing this by enumerating menu entries from each instance and creating a composed whole. Enumerating the active applications from each instance and composing them into a single "task bar"/"window switcher" interface.

this is probably close to 20 years old now.

Re: State of multi-player Wayland

#115
one interesting use case is surface management in ways that cant be solved easily by swapping desktops or which is clunky this happens most on single-screen where have to swap apps out that have related actions and want to rearrange or copy paste between or scroll sync and native app so cant scroll sync by extension think rapid fire macro mouse events except not just serial which can run the experience eg browser tab and electrion app that sync scroll or scroll c/p and where macro recorder might come close but not really
Post reply on HN