"LIBOUTPUT" Proposed As New Library For Helping To Bring Up New Compositors & More

[phoronix]

Phoronix: "LIBOUTPUT" Proposed As New Library For Helping To Bring Up New Compositors & More

Coming out of informal discussions from this week's X.Org Developers Conference in Montreal, a "liboutput" library has been proposed as a theoretical new library for helping to bring up Wayland compositors, X11 window managers, and anything else wanting to interface with DRM/KMS kernel interfaces...

http://www.phoronix.com/scan.php?page=news_item&px=LIBOUTPUT-Proposal

[tildearrow]

We already have libweston, wlroots and Mir.

[kpedersen]

Honestly, everyone is just waiting for a libX11 API layer to be built on top of Wayland. Then people can stop faffing around and get back to some real work XD.

[babali]

Honestly, everyone is just waiting for a libX11 API layer to be built on top of Wayland. Then people can stop faffing around and get back to some real work XD.

That is more or less XWayland...

[Tomin]

There would be proper support for multiple plans, making use of the KMS leasing infrastructure, projective transforms, multiple output handling, atomic presentations, and other bits.

Or planes?

[kpedersen]

That is more or less XWayland...

Yes, I suppose that is true

And whats great about this "innovative design" is that when Wayland has become deprecated, we can have a simple XNextbestthing implemented to replace XWayland and all of the great libX11 software can still function

[microcode]

We already have libweston, wlroots and Mir.

I think this is more generic than that. I wanted to write a direct DRM/KMS application a couple months ago and it was daunting.

[miabrahams]

We already have libweston, wlroots and Mir.

I do not understand these libraries well enough to know exactly how this relates. I think libweston, wlroots and this are somehow similar, while Mir is a compositor that could (theoretically) be rebased to rely on one or more of these libraries. But what roles do these things fill precisely, and what is the supposed value-added of liboutput?

[tildearrow]

I do not understand these libraries well enough to know exactly how this relates. I think libweston, wlroots and this are somehow similar, while Mir is a compositor that could (theoretically) be rebased to rely on one or more of these libraries. But what roles do these things fill precisely, and what is the supposed value-added of liboutput?

Mir has MirAL, which is very similar to libweston and wlroots in the sense that it can be used to aid in the making of compositors.

[ivyl]

Oh, this looks like it is takes some inspiration from libliftoff that was discussed during XDC just a few days ago. It also looks like it also tries to integrate some of the wlroots backend bits.

https://xdc2019.x.org/event/5/contributions/586/

https://github.com/emersion/libliftoff