[vlc-devel] [PATCH 00/14] Move VLM implementation to a module

Rémi Denis-Courmont remi at remlab.net
Sat Sep 19 08:41:15 CEST 2020


Le lauantaina 19. syyskuuta 2020, 8.25.29 EEST Pierre Ynard via vlc-devel a 
écrit :
> > And then you have indirect uses: VLM is the backend, but the VLC
> > 4.0 player or playlist could advantageously be used instead - HTTP
> > interface and GUIs.
> 
> It doesn't help that interfaces usually take the approach of offering
> a VLM dialog to allow users to access the VLM to do whatever VLM stuff
> they want, rather than offering a feature dialog that internally uses
> the VLM as a back end for a specific purpose.

Handling VLM via Lua was first meant to replace the so-called "telnet" C 
module. Then passing VLM commands via Lua/HTTP was an easy addition. I never 
understood exposing VLM with Qt though. That seems like such a misfit with the 
rest of the GUI.

> In fact this is more akin to a solution looking for a problem; and I
> think that's exactly the contrary of what we should be doing with the
> VLM.

Historically, I think it's really just lazy programmer' shortcuts. First 
Laurent made the parser as the least effort PoC for multiple input, and then 
Antoine exposed the parser to Lua.

Still, I don't think that there is currently a proper interface for private 
player or playlist instance in Lua, so it's at minimum a little premature to 
remove VLM from there.

-- 
雷米‧德尼-库尔蒙
http://www.remlab.net/





More information about the vlc-devel mailing list