On Mon, 19 Dec 2016 10:50:22 +0100 Christian Stroetmann <stroetm...@ontolab.com> wrote:
> On19.Dec.2016 09:48, Pekka Paalanen wrote: > > Sorry for not realizing the "wrap libEGL.so" approach earlier. > > Yeah, and how does this look like when put in context with Waltham? It has nothing to do with Waltham at all. It is completely orthogonal. You still have the Wayland compositor beside the application, and the compositor is still serving Wayland clients and using something else on the network. It could be waltham or RDP or VNC or HTTP... neither the application nor the wrapper-libEGL would care. The libEGL.so wrapper could help by converting the application output to wl_shm in the application process, which is the alternative to implementing support in the compositor for handling all the different hardware-related buffer types. Both ways presumably work, and with slightly different characteristics. Thanks, pq
pgp5gIN3RrUqi.pgp
Description: OpenPGP digital signature
_______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
