[vlc-devel] Re: Proper separation of GUI and engine

[NeBlackCat (lists)]

Ok, thanks for that clarification. I'm going to keep reading up on VLC 
(I've spent the weekend doing that as well as reading about Xine, 
Mplayer, GStreamer, BASS, Audiere, FMOD, etc, etc, having had no 
exposure to any of this stuff before, and my head is spinning) with a 
view of working out whether I could perhaps do the "addressing this" at 
some point.

Rémi Denis-Courmont wrote:
> Le dimanche 13 mai 2007, NeBlackCat (lists) a écrit :
>   
>> Hello again,
>>
>> I was wondering, are there any plans to properly "libraryize" VLC so
>> that it is a shared library with a comprehensive, well defined API
>> that provides access to all of it's functionality, and a separate
>> GUI(s)?
>>     
>
> We already have libvlc as a shared object.
>
> The only and main problem is that the API/ABI is a bit unstable from 
> version to version. However, addressing this is a huge work which does 
> not bring any user-visible improvement, so it is not going to happen.
>
> The media control API is a compromise that gives access to the basics 
> through a more stable API/ABI, and that's probably what you are looking 
> for.
>
> In any case, this is GPL'd work, which is probably why big players are 
> putting money to LPGL'd gstreamer instead of Xine, Mplayer and VLC.
>
>   

-- 
This is the vlc-devel mailing-list, see http://www.videolan.org/vlc/
To unsubscribe, please read http://developers.videolan.org/lists.html