From: Michael R. <mr...@us...> - 2005-02-02 20:03:39
|
Hi, > I'm currently looking at the xine-lib API and how to write video-out > plugins and considering how to integrate it with the OSG, as per the thread > "Integrating xine-lib with a realtime graphics library" which I kick off. > > One element that it would like control is be an explicit creation of my own > video-out driver/port via a mycustom_create_video_out_port(..) call to > replace the traditional xine_open_video_driver(..) mechansim utilised in > example application code. I do not understand the need for this. You can create your own visual type and establish an arbitrary communication channel between your plugin and the calling app through the structure passed as the fourth argument of xine_open_video_driver(). Reimplementing a customized xine_open_video_driver() call would need a lot of assumptions on xine internals which are not part of the public API, so your code is not guaranteed to work with future versions of xine-lib. > This would allow me to keep all the custom video driver code local to my > OSG plugin, without the need to special xine-lib plugin needing to be > installed. So what you actually want is statically linked plugins. I am sure this need can be satisfied easily. Michael -- printk(KERN_WARNING "Multi-volume CD somehow got mounted.\n"); 2.2.16 /usr/src/linux/fs/isofs/inode.c |