[vlc-devel] [PATCH] QT4 playlist: even better DragNDrop policy

Pierre d'Herbemont pdherbemont at free.fr
Tue Aug 11 20:40:27 CEST 2009

On Aug 11, 2009, at 6:19 PM, Jean-Baptiste Kempf <jb at videolan.org>  

> Hello,
> On Tue, Aug 11, 2009 at 05:34:01PM +0200, Jakob Leben wrote :
>> Well, eventually somebody will have to start somewhere, I guess.  
>> Any plans
>> on when to start porting? How ready and how complete is the new  
>> libvlc
>> anyway? As much as I "surfed" and "deciphered" the current vlc  
>> code, the vlc
>> executable itself already uses libvlc, and on the other hand libvlc  
>> uses
>> some of the current code (like input_item_t - withing  
>> libvlc_media_t). Will
>> eventually the external api consist only of what is inside include/ 
>> vlc, so
>> that for example input_item_t will not be dealt with from outside  
>> at all?
>> I'm offering myself to code at least the Qt4 media list model using  
>> new
>> libvlc. Doesn't seem to me too hard a job and I've got very  
>> aquanted with
>> Qt4 model/view architecture by now. What do you say?
> I don't think this is the good solution.
> - libvlc is very limited compared to a libvlccore module.

It is, but there is not many *useful* thing that you wouldn't be able  
to do from libvlc, that you usually do from libvlc core. Extending it  
is trivial. Using libvlccore directly could still be an option, if you  
link to libvlc.

I would strongly encourage to build a qt4 interface on top of libvlc.  
I think you would be surprised to see how much you would gain in term  
of simplicity.

You would also gain supporting multiple video at the same time within  
the same instance. This is as anecdotical as multiple interface but  
it's worth mentionning.

However I would admit that this would take much more man hours to  
develop that what you would expect. And that this is a brand new  


More information about the vlc-devel mailing list