[vlc-devel] [PATCH] QT4 playlist: even better DragNDrop policy
remi at remlab.net
Tue Aug 11 19:35:04 CEST 2009
Le mardi 11 août 2009 20:10:22 Jakob Leben, vous avez écrit :
> On Tue, Aug 11, 2009 at 6:19 PM, Jean-Baptiste Kempf <jb at videolan.org>wrote:
> > I don't think this is the good solution.
> > - libvlc is very limited compared to a libvlccore module.
> > - Having more than 1 interface (Qt+Web) is nice.
> So, to sum up and to see if I understand the situation:
> - libvlc does not load interfaces as modules, interfaces are supposed to be
> built on top of libvlc and it doesn't know about them
External applications are supposed to be built on top of libvlc. Expectedly,
their interface will sit on top of libvlc, not as a plugin to libvlc.
> - however, libvlc does use most of what are now modules (it has to demux,
> decode and play), right?
> - but libvlc user does not have control over which modules are loaded
> (probably all available or the ones that are needed to play current media)
Modules are loaded more or less automatically, yes
> - the old api, or let's say vlc executable will persist.
There is no old API (anymore).
There is an internal/unstable API for modules, and an external/stable API for
third party applications and language bindings.
> - therefore development of Qt interface used by vlc executable is
I don't understand what you mean.
More information about the vlc-devel