[MeeGo-touch-dev] grab XWindowID from MTF applications

[Gerry LaChac]

On 09/13/2010 09:52 PM, Alexander Bokovoy wrote:
> On Tue, Sep 14, 2010 at 03:27, Zhao, Halley<halley.zhao at intel.com>  wrote:
>    
>> I fully agree with your concerns. GStreamer provides more flexibility.
>> In fact, the gap between your gst based application and Qt (QGraphicsview) is just a Qt video sink for GStreamer, which could render video frame as texture in QGraphicsView.
>> You can create such sink in a separated library refer to QGraphicsVideoItem in qt-mobility; then your video conference, TV player, camera, video player can build base on it.
>>      
> This "just" highly depends on what actual hardware you are working
> with. Getting every single frame into texture is expensive on some
> hardware. For example, it is very slow on N900 without so called
> texture streaming capability which is not supported by N900's graphics
> drivers properly.
>
> So, yes, it is possible, but end result is not really pleasing and usable.
>
>    

It also seems complicated to a video rendering novice.  I quickly looked 
at QGraphicsVideoItem and on first glance I'm somewhat lost on the new 
terminology.  With gstreamer and xvimagesink all I needed was to connect 
to existing widgets I've already have experience with.  With this 
solution, it seems I have to delve into understanding video mapping 
techniques and opengl, something that previously was hidden in a nice 
library.

Is there a pointer to somewhere I can read up on "texture streaming" and 
the other concepts going on here?  The qt-mobility docs I've seen seem 
to assume some pre-existing knowledge.