<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 21/09/2020 03:20, Pierre Ynard via
vlc-devel wrote:<br>
</div>
<blockquote type="cite"
cite="mid:mailman.5586.1600651234.12816.vlc-devel@videolan.org">
<blockquote type="cite" style="color: #000000;">
<pre class="moz-quote-pre" wrap="">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.</pre>
</blockquote>
</blockquote>
<p>Deprecating without an equivalent solution is really weird.<br>
</p>
<p>
</p>
<blockquote type="cite"
cite="mid:mailman.5586.1600651234.12816.vlc-devel@videolan.org">
<blockquote type="cite" style="color: #000000;">
<pre class="moz-quote-pre" wrap="">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.
</pre>
</blockquote>
</blockquote>
<p>This is exactly what was tried:</p>
<p>- new player + playlist to avoid input/player duplication (mostly
done)<br>
</p>
<p>- move VLM file parsing to a new module (whatever the type) and
have the player/playlist handle the features required, so that
that modules does only parsing + spawning of various players.</p>
<p>- have the VLM module understand most of the VLM file syntax.</p>
<p>So I'm not sure in what way what you are suggesting is different
from the current approach.</p>
<p>As for dedicated libVLC application, I already explained why I
was against this.<br>
</p>
<p><br>
</p>
<pre class="moz-signature" cols="72">--
Jean-Baptiste Kempf
<a class="moz-txt-link-freetext" href="http://www.jbkempf.com/">http://www.jbkempf.com/</a> - +33 672 704 734
Sent from my Electronic Device</pre>
</body>
</html>