@GyrosGeier
This, but then awesomewm.
I think a more globally useful approach would be to write something that implements the part of an X11 server that the window manager talks to, but that looks like Wayland to the applications. This way, people who really don't want to migrate away from their X11-only environment can keep using it and still use Wayland.
This is probably naive and not possible, but meh, one can dream.
@ignaloidas @mjg59
This, but then awesomewm.
I think a more globally useful approach would be to write something that implements the part of an X11 server that the window manager talks to, but that looks like Wayland to the applications. This way, people who really don't want to migrate away from their X11-only environment can keep using it and still use Wayland.
This is probably naive and not possible, but meh, one can dream.
@ignaloidas @mjg59
@ignaloidas
My understanding of Wayback was that it is a way to provide an X11 implementation that uses the Wayland backend, rather than a way to shoehorn the Wayland frontend under an X11 window manager, which is what I'm suggesting.
Of course my understanding can be wrong, in which case a link to more information would be welcomed by a promise for your favourite beverage at my cost if you look for me at the next FOSDEM 😉
@mjg59 @GyrosGeier
My understanding of Wayback was that it is a way to provide an X11 implementation that uses the Wayland backend, rather than a way to shoehorn the Wayland frontend under an X11 window manager, which is what I'm suggesting.
Of course my understanding can be wrong, in which case a link to more information would be welcomed by a promise for your favourite beverage at my cost if you look for me at the next FOSDEM 😉
@mjg59 @GyrosGeier
@ignaloidas
Not quite.
These are all 'I have a native Wayland application that I want to run in my X11 session'. That's a cool thing, but not what I want to do.
I want to *run* a Wayland environment. Everything should be Wayland, with standard fallback to the XWayland thing for stuff that isn't supported yet.
Except that I just want the UI to be a window manager that expects X11.
@mjg59 @GyrosGeier
Not quite.
These are all 'I have a native Wayland application that I want to run in my X11 session'. That's a cool thing, but not what I want to do.
I want to *run* a Wayland environment. Everything should be Wayland, with standard fallback to the XWayland thing for stuff that isn't supported yet.
Except that I just want the UI to be a window manager that expects X11.
@mjg59 @GyrosGeier
@ignaloidas
To put it otherwise.
I think what I want is a Wayland compositor that doesn't provide a UI, but that instead provides some sort of compatibility layer so you can hook up a window manager to do the actual UI work.
@GyrosGeier @mjg59
To put it otherwise.
I think what I want is a Wayland compositor that doesn't provide a UI, but that instead provides some sort of compatibility layer so you can hook up a window manager to do the actual UI work.
@GyrosGeier @mjg59
- replies
- 1
- announces
- 0
- likes
- 0
@GyrosGeier
Yes, that's what I mean.
Would be awesome because suddenly every window manager "works" with Wayland.
Probably not a good idea though because everything will be very confused.
@ignaloidas
Yes, that's what I mean.
Would be awesome because suddenly every window manager "works" with Wayland.
Probably not a good idea though because everything will be very confused.
@ignaloidas
@GyrosGeier
These kinds of issues are why I said "works" rather than the plain unquoted variant of that word 😉
@ignaloidas
These kinds of issues are why I said "works" rather than the plain unquoted variant of that word 😉
@ignaloidas
@GyrosGeier
Still, if needing extra VRAM may be a reasonable price to pay for some if it means they can move to something more modern without leaving their UI behind.
@ignaloidas
Still, if needing extra VRAM may be a reasonable price to pay for some if it means they can move to something more modern without leaving their UI behind.
@ignaloidas