[MPlayer-dev-eng] [RFC][PATCH]removing gmplayer

[Benjamin Zores]

On Sat, Jun 12, 2010 at 12:05 PM, Diego Biurrun <diego at biurrun.de> wrote:
> On Fri, Jun 11, 2010 at 07:10:14PM +0200, Reimar Döffinger wrote:
>> On Fri, Jun 11, 2010 at 11:17:24AM +0200, Diego Biurrun wrote:
>> > On Fri, Jun 11, 2010 at 12:17:43AM +0200, Reimar Döffinger wrote:
>> > > Right now I don't see a real cost in keeping it, slowly squezzing out remaining
>> > > users via rot.
>> >
>> > The costs are very real code complexity and ugliness.  The GUI is badly
>> > architected.  It should not spread its fingers all over the core code.
>>
>> Any particularly bad issue?
>> E.g. I think it's okay to just remove the GUI code from mp_msg, but I wasn't
>> able to find any other significant GUI code under CONFIG_GUI _except_ a huge
>> load in vo.
>>
>> > What made you change your mind?  Last time you said that if no maintainer
>> > is found, we should drop it.  After 1.0rc4 is the best moment for that.
>>
>> Did I? I remember it more like it being acceptable to drop it.
>
> We talked about this at froscon I think.  You said that we might make
> an announcement together with 1.0rc4 that the GUI will go the way of
> the dodo unless some person steps up to maintain it.
>
> Nobody will step up to maintain it, it's a complete dead end.

Just my .02$ but this has already been discussed years ago and there's
still no maintainers for this.
Nobody ever uses it, no development is made against it anymore and
devs recommend not to use it.

So what's the point of the GUI except for adding maintenance complexity ?
You want more devs to be involved in MPlayer right ? And I remember
many patches having to be adapted just to take the GUI into account.
It's a burden, period.

Anyhow, adding a --enable-deprecated-gui (or whichever configure
option) won't help much if nobody ever checks if it's actually
compilable.

Ben