From: Robert O. <ro...@op...> - 2005-02-02 21:11:23
|
Hi Michael, On Wednesday 02 February 2005 20:03, Michael Roitzsch wrote: > > 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. I am not talking about customizing xine_open_video_driver(), but calling other existing xine functions to avoid the plugin loading mechansim and then wrapping this up inside my own convinience function. Since if the actual driver implementation is part of the calling code then its already explitly known about, and I not need an extra level of indirection that the current xine_open_video_driver(..) approach forces. It might be that another function or functions need to be added to xine-lib to add this flexibility, if I do modify anything I would want to do it in keeping with the rest of xine-lib and would hope that such change could be integrated with xine-lib main branch. > > 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. I rather not statically link, it'd be much simpler on my own plugin wiritng side to just have one OSG plugin with all the required code in one place and building into a single .so. Requring a second custom plugin to be written just to satisify the current xine-lib plugin mechansim would hardly be a good engineering solution, especially if xine-lib can already do what I require if used the correct way. There may be other solutions, such as Matthias' suggestion of a general rtf plugin, with my own plugin linking to xine-lib and just requesting the load of the rtf plugin. This might be solution, but even then won't be as robust a solution as including the driver code directly into an OSG plugin, as the later wouldn't require a rtf plugin to be part of xine-lib distribution and installed on the end user system. -- So my question still stands, would be it possible to use my own video driver directly rather then current xine_open_video_driver(..) method. Looking at the code I expect it should be possible, albiet perhaps with a few minor tweaks or an extra convinience method, however, I'm not expert on xine-lib which is why I ask the question. Cheers, Robert. |