Re: zwp_fullscreen_shell_v1
On Wed, Jan 08, 2020 at 10:11:40AM +, Alan Griffiths wrote: > On 08/01/2020 10:01, Jonas Ådahl wrote: > > This idea has more or less been abandoned however, so I'd say it's more > > likely we can "archive" it rather than marking it as stable, as there > > are as far as I know no real users of it. > > Thanks for that > > > For kiosk mode, you still probably want to use xdg-shell, as it's not > > unlikely the kiosk application still wants to use things like popup > > surfaces for drop down menus etc. Your compositor can, when in kiosk > > mode, for example only allow one client, with only a single toplevel, > > that is always configured as fullscreen. > > Yes, we do that already. I was looking for an approach that also allows > the app to configure, for example, the screen resolution. You could effectively achieve that by letting the application use the viewport extension to scale the surface in any way it sees fit; your compositor can then set the most appropriate resolution according to the actual surface dimensions. Jonas > > Alan > > ___ > wayland-devel mailing list > wayland-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/wayland-devel ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: zwp_fullscreen_shell_v1
On 08/01/2020 10:01, Jonas Ådahl wrote: > This idea has more or less been abandoned however, so I'd say it's more > likely we can "archive" it rather than marking it as stable, as there > are as far as I know no real users of it. Thanks for that > For kiosk mode, you still probably want to use xdg-shell, as it's not > unlikely the kiosk application still wants to use things like popup > surfaces for drop down menus etc. Your compositor can, when in kiosk > mode, for example only allow one client, with only a single toplevel, > that is always configured as fullscreen. Yes, we do that already. I was looking for an approach that also allows the app to configure, for example, the screen resolution. Alan ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: zwp_fullscreen_shell_v1
On Wed, Jan 08, 2020 at 09:46:13AM +, Alan Griffiths wrote: > Hi, > > with Mir's "mir-kiosk" being deployed for running single, fullscreen > apps there are requests for ways that the apps can control the output > mode. Looking at zwp_fullscreen_shell_v1 this appears to meet many of > these requirements. However, it is "unstable" and I don't see evidence > of it being widely used. > > So, what is the status of this extension protocol? Is it mostly > forgotten? Or just waiting for a final push to stable? The use case in mind when the fullscreen shell was written was making it possible for compositors to outsource KMS and evdev integration to a parent compositor, making it possible to write a compositor with only a Wayland backend, then using e.g. weston and its fullscreen shell implementation to make it possible to run seemingly native. Input would be routed as regular wl_pointer, wl_keyboard events etc, and things like plane assignment would be done by having the nested compositor use subsurfaces. This idea has more or less been abandoned however, so I'd say it's more likely we can "archive" it rather than marking it as stable, as there are as far as I know no real users of it. For kiosk mode, you still probably want to use xdg-shell, as it's not unlikely the kiosk application still wants to use things like popup surfaces for drop down menus etc. Your compositor can, when in kiosk mode, for example only allow one client, with only a single toplevel, that is always configured as fullscreen. Jonas > > Thanks, > Alan > > ___ > wayland-devel mailing list > wayland-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/wayland-devel ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
zwp_fullscreen_shell_v1
Hi, with Mir's "mir-kiosk" being deployed for running single, fullscreen apps there are requests for ways that the apps can control the output mode. Looking at zwp_fullscreen_shell_v1 this appears to meet many of these requirements. However, it is "unstable" and I don't see evidence of it being widely used. So, what is the status of this extension protocol? Is it mostly forgotten? Or just waiting for a final push to stable? Thanks, Alan ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
