On Fri, May 01, 2015 at 08:01:34PM +0300, Tone Kastlunger wrote: > I'd guess this would require patching lipstick (compositor) as well? > tortoisedoc
I cannot tell. One option is to use wayland subsurfaces (I don't know if it's even possible or not). We can then extend droideglsink to use subsurfaces and let the compositor do the work. I would not prefer giving the buffers themselves to the app for rendering because: 1) There is no guarantee that the content of the buffers will be cross platform. We get a vendor specific data format encapsulated within an android buffer and we do not even know (from a programming POV) what the format of the data is 2) If the app blocks, the decoding pipeline will stall. We can push up to 2 buffers only to the app and if we don't get them back to the decoder we will block and stop decoding. 2 is what we are limiting ourselves to currently but could increase in the future. An alternate way is to patch glimagesink from plugins-bad to grok our buffers or to enable waylandsink and ship it. Cheers, _______________________________________________ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
