[vlc-devel] Deprecating the VLM

[Romain Vimont]

On Mon, Sep 21, 2020 at 03:20:29AM +0200, Pierre Ynard via vlc-devel wrote:
> Date: Mon, 21 Sep 2020 03:20:29 +0200
> From: Pierre Ynard <linkfanel at yahoo.fr>
> To: vlc-devel at videolan.org
> Subject: Deprecating the VLM
> User-Agent: Mutt/1.5.23 (2014-03-12)
> 
> > And I would like to propose deprecating the VLM. I would like to
> > propose that we agree to stop development of it or around it: no more
> > new features, no new APIs or exported symbols, no more exposing it
> > through new interfaces (for example #2887), and no new developments
> > based on it or integrating around it. We can print a deprecation
> > notice upon loading, and mark the API calls as deprecated. And then
> > we can also stop wasting time and efforts on patchsets and arguments
> > about VLM developments.
> 
> > So in addition to deprecating the VLM, I would also like to ask
> > whether anyone is opposed to the principle of 1/ migrating existing
> > multiple-input management in interfaces away from transparent VLM
> > exposure to proper core APIs and UX, and 2/ migrating features
> > requiring single-instance multiple inputs away from the VLM to
> > dedicated control interfaces, or maybe possibly dedicated LibVLC
> > applications. This would look to me like a sound alternative and way
> > to go, even if nobody puts resources into it right now. This wouldn't
> > preclude ongoing additional work on core subsystems to accommodate it.
> 
> I'm surprised that this got little direct response. JB, Romain,
> everybody else? What do you think, is that okay with you? I've submitted
> a patch kind of meaning to enact this.

Hi Pierre,

Thank you for your contribution to the discussion. Sorry for not having
answered.

The reason is just that I don't know what we should do with VLM, I don't
know if it's ok or not, so for now I'm just reading the discussions and
opinions about this.

Regards