Hello Nicolas, the ilm api is implemented for the ivi (in vehicle infotainment) window management and allow to control applications surfaces outside from the compositor, it is realized by the ivi-shell in weston. with ivi-shell every weston surface have to have an id assigned to it (very simple ivi-application protocol is defined for this) and the ilm control api can use the id to reference the surface.
@Vikas so in general I will not use the ilm Client api's in the middleware components, by just using the ivi-application wayland protocol we can decide dynamically if the protocol is available and register the id if not do something else: e.g. xdg surface setup. The ivi controller (hmi master, hmi application controller or however it is called) should still use the ilm controller api's to control the composition. 2017-03-28 16:01 GMT+02:00 Nicolas Dufresne <nico...@ndufresne.ca>: > Le mardi 28 mars 2017 à 12:18 +0530, Vikas Patil a écrit : >> Hi Eugen, >> >> Yes, I have implemented using protocol and it is working. However I >> also want to try it with direct usage of ILM apis but no luck yet. I >> have done the same with glimagesink, eglvivsink video sink plugin and >> it is working. > > What is that ILM library ? Why shall be add a new deps to that library > in GStreamer ? > > regards, > Nicolas _______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel