You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ChromeOS is increasingly becoming a valid Wayland platform, moving into a common direction with the FDO world. I.e. adopting upstream protocols and upstreaming private ones. Thus supporting it could increasingly be of interest for Linux app/toolkit developers.
Exo is the system Wayland compositor which soon will even be used by the internal Chrome browser (see the Lacros project, turning it into a Linux/Wayland Chromium for the most part - instead of using internal widgets/protocol).
Non-system apps can't use Exo directly though. Linux apps they live in containers which have some kind of "proxy" Wayland compositor (Sommelier), which also manages the individual Xwayland instances - each app container has an own one. I.e. apps talk to their in-container Wayland compositors, which then talk to the (one) Exo system compositor.
Thus the protocols exposed to apps depend (more or less) on the combined capabilities of Exo and Sommelier. That's why I'd like to suggest to introduce a combined section for them - either as ChromeOS or something like Exo+Sommelier.
If people like/support the idea I'd look into making an initial MR and maintaining it (on a similar level to other compositors - i.e. updating maybe twice a year).
The text was updated successfully, but these errors were encountered:
Sorry for the late reply. Adding support for ChromeOS is a feature that would be very nice to have (e.g.: both for listing their custom protocols and for adding ChromeOS to the compositor support tables). So a pull-request adding support for it would definitely be welcome.
+1 from me as well, obviously you would have to update the support tables yourself from time to time, as my setup for updating the tables is just an Arch VM that will definitely not be able to handle this.
As far as wlprobe goes, it should run fine on ChromeOS, but feel free to ping me if you encounter any problems with it, you definitely don't want to update the list manually 😄
ChromeOS is increasingly becoming a valid Wayland platform, moving into a common direction with the FDO world. I.e. adopting upstream protocols and upstreaming private ones. Thus supporting it could increasingly be of interest for Linux app/toolkit developers.
Exo is the system Wayland compositor which soon will even be used by the internal Chrome browser (see the Lacros project, turning it into a Linux/Wayland Chromium for the most part - instead of using internal widgets/protocol).
Non-system apps can't use Exo directly though. Linux apps they live in containers which have some kind of "proxy" Wayland compositor (Sommelier), which also manages the individual Xwayland instances - each app container has an own one. I.e. apps talk to their in-container Wayland compositors, which then talk to the (one) Exo system compositor.
Thus the protocols exposed to apps depend (more or less) on the combined capabilities of Exo and Sommelier. That's why I'd like to suggest to introduce a combined section for them - either as
ChromeOS
or something likeExo+Sommelier
.If people like/support the idea I'd look into making an initial MR and maintaining it (on a similar level to other compositors - i.e. updating maybe twice a year).
The text was updated successfully, but these errors were encountered: