Compositor ideas about wlroots HOT 5 CLOSED

wlroots isn't actually going to render surfaces for you at all or even keep track of their x/y coordinates. You'll definitely be able to implement a feature like that, since most of the work will be on your side anyway.

from wlroots.

One of the features I would like to have for Way Cooler is to have multiple surfaces displaying content from the same client (and for them all to be able to be interacted with). This would allow me to implement tags (as an alternative to workspaces) and is currently not possible with wlc due to its strict one to one mapping of view to surface.

Do you think the surface creation code will be able to be exposed enough to make that possible in wlroots? Would it be able to be done in a backend agnostic way?

Here is an example of what I'm talking about implemented weston

from wlroots.

To clarify, wlroots will render surfaces for you if you ask it to. But it won't be automatic, it'll be a function you call during your output_frame handler and provide x/y coords and a surface to render.

from wlroots.

I don't know where in the stack that needs support, but the rotation feature of weston is epic.
BTW does this wlroots complement or replace libweston and qtwayland?

@plfiorini: might be applicable to Liri OS?
@sardemff7: intersection/integration with wayland-wall?

from wlroots.

All the stuff wlroots needs to implement to support rotation is already in place.

wlroots replaces libweston/qtwayland/wlc.

Don't expect much in the way of wayland-wall integrations.

from wlroots.