Re: [xine-devel] bug: deadlock in xine_close_video_driver with paused stream and rewireing

[Michael R. <mr...@us...>]

Hi Stefan,

> > Interesting. What is this project going to be?
>
> the core of xiron consists of a xml parser, a java-script interpreter,
> an event passing system, a resource management and a module loader based
> on shared libraries (just like xine-lib). the kernel parses xml files to
> instantiate a set of modules and interconnect them to form a media
> player. for example:
>
> <xiron version="1.0">
>   <x11>
>     <video w="640" h="480" title="x11 video window" />
>     <video id="video2" driver="xshm" w="320" h="240"
> 	   title="post plugin output" />
>   </x11>
>   <audio />
>   <visualization type="goom" id="goom" video="video2" audio="audio" />
>   <player audio="goom" />
>   <playlist />
>   <eventmap>
>     <buttonpress key="page-down" eval="playlist.current++;" />
>     <buttonpress key="page-up" eval="playlist.current--;" />
>   </eventmap>
> </xiron>
>
> each of the xml tags here (except of 'buttonpress'-tags) instantiates a
> module of the appropriate class. two video windows are opened and the
> video ports are exported as resources. the visualization module then
> connects to the ports 'video2' and 'audio', the player (which represents
> a xine stream) connects to the audio port of 'goom' and (implicitly) to
> 'video'. on shutdown of xiron, the order of module destruction is
> undefined (except that child modules are destroyed before its parents).
> it is indeed possible, that the video modules are destroyed first and
> revoke its video-port-resources. the visualization and player modules
> must take care of this and disconnect properly. all this is done using
> rewireing.
>
> it is planned that the whole ui and its behavior is defined by xml and
> js files (some very simple osd and gtk2 modules exist for now), so that
> xiron can become every desired frontend without recompilation. i plan
> the first release (0.1) in a week or so. of course the public cvs is
> already available and if someone wants to help me the this project,
> (s)he is greatly welcome :-).

So this is basically a framework for rapid/dynamic xine frontend creation. 
Very cool! We should put this on xinehq when it is released.

Michael

-- 
This message transmitted on 100% recycled electrons