[MPlayer-dev-eng] c++ version of mplayer.c

[Martin Drab]

On Fri, 11 Feb 2005, Jan Volf wrote:

> On 11.2.2005, at 19:06, Martin Drab wrote:
> 
> > It makes possible to write the GUI in whatever crappy language you decide
> > (C++, Java, Perl, Python, ... or whatever the GUI guys like the most)
> > without polluting MPlayer's sources with that. And I consider that
> > quite important.
> 
> Hmm, it seem that our personal feelings are quite different. Anyway I don't
> want to pollute code of mplayer with my GUI code. All I want to do is
> completely opposite, remove any UI code from mplayer's core code, separating
> the high level (UI) code from low level (core) and create some kind of
> interface between them.

I'm not opposed to this. But how would this interface look like? It would 
be nice if mplayer wouldn't have to be binarily integrated into each of 
its GUIs that would be installed on the system. Pipes are a good way of 
separation. You may have as many different GUIs as you want and just one 
MPlayer for them, which could also be used completely without the GUIs 
(kind of like cdrecord for instance).

> The present mplayer's code is polluted (like you're
> saying) with CLI UI code and even with GTK UI code. All is mixed together with
> mplayer's core code - quite a mess :).

Agreed.

> Then I can simply take that code and incorporate it in to my GUI code and
> produce nice well-behaved application for OS that I'm developing for. And I
> thought that someone would welcome it and write the same way the GUI for his
> favorite OS and so on for another OSes.
> I don't think it's a bad idea, don't you?

Indeed.

Martin