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

[NeBlackCat (lists)]

Yes I know, but (as I understand it) they provide a small number of 
simple, high level functions (play media, go full screen, add to 
playlist, etc) whereas (for example) Xine's API exposes all of Xine's 
guts, so you can do all sorts of low, medium and high level media 
related stuff through it.

In other words (as I understand it) VLC is a media player with an API to 
allow you to control it. OTOH Xine is a media library that you can build 
a media player around. So my question was whether VLC would be 
repackaged along the Xine lines.

I hope that makes sense, I might not be explaining this very well! :-)

Pierre d'Herbemont wrote:
>
> On 13 mai 07, at 13:09, NeBlackCat (lists) wrote:
>
>> 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)?
>
> There are already two ways to use VLC core as a library, see
> http://wiki.videolan.org/MediaControlAPI
> based on
> http://wiki.videolan.org/ExternalAPI
>
> Pierre.
>

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