Might be worth Investigating a GBM & DMA-BUF backend similar to what wpewebkit have done with libwpe. WebkitGTK will be dropping support for their nested Wayland compositor in favour of libwpe going forward in a plan is to simplify how they are delivering their X11/Wayland support.
I'd imagine that this could be a potential path towards embedding ShaftUI in native codebases through the import of DMA-Buf's as textures for e.g a GTK4 embedder, GTK3 embedder, Qt Embedder etc to ingest.
This could also be used to bootstrap a wpewebkit webview widget.
Overall thinking about zero copy texture sharing seems like the correct approach if we want ShaftUI to run on Linux natively and performantly and without any hard dependencies on third party toolkit embedding.
Might be worth Investigating a GBM & DMA-BUF backend similar to what wpewebkit have done with libwpe. WebkitGTK will be dropping support for their nested Wayland compositor in favour of libwpe going forward in a plan is to simplify how they are delivering their X11/Wayland support.
I'd imagine that this could be a potential path towards embedding ShaftUI in native codebases through the import of DMA-Buf's as textures for e.g a GTK4 embedder, GTK3 embedder, Qt Embedder etc to ingest.
This could also be used to bootstrap a wpewebkit webview widget.
Overall thinking about zero copy texture sharing seems like the correct approach if we want ShaftUI to run on Linux natively and performantly and without any hard dependencies on third party toolkit embedding.