[vlc-devel] [PATCH] [RFC] input: set "input-current" early so control interfaces can control earlier

Steve Lhomme robux4 at gmail.com
Tue Nov 24 08:55:24 CET 2015


On Mon, Nov 23, 2015 at 7:05 PM, Rémi Denis-Courmont <remi at remlab.net> wrote:
> On Monday 23 November 2015 18:25:27 Steve Lhomme wrote:
>> But one of the goals of the Chromecast is to serve as an output for
>> whatever you play in your regular VLC.
>
> I don´t care™.
>
>> And that playback happens via the playlist. We don't want to create a
>> secondary player or UI (with a list of files to play) just for that.
>
> *You* don´t want to create a secondary player. *I* don´t want to break the
> existing code and user interfaces.
>
>> What do you mean conflict with each other ?
>
> I am not going to paraphrase it.
>
>> What kind of things are control interfaces allowed to do and not do ?
>
> Could you, like, look around the code base to answer your own questions? I
> have much more interesting things to do with my free time than code review and
> architectural documentation.

The problem is that if I hit unwritten rules, I have no way to find
beforehand. For example this patch doesn't break any unwritten rule,
as far as I can tell. It makes the Chromecast "control interface"
module work just fine.

But anyway we can discard it as I want a solution that works for
libvlc too. So the module cannot depend on the playlist too much.

> --
> Rémi Denis-Courmont
> http://www.remlab.net/
>
> _______________________________________________
> vlc-devel mailing list
> To unsubscribe or modify your subscription options:
> https://mailman.videolan.org/listinfo/vlc-devel


More information about the vlc-devel mailing list