[MPlayer-dev-eng] An attempt at libmplayer

Reimar Doeffinger Reimar.Doeffinger at stud.uni-karlsruhe.de
Thu Sep 11 15:30:45 CEST 2008


On Thu, Sep 11, 2008 at 02:35:31PM +0200, Attila Kinali wrote:
> make all subsystems reentrant
> and thread safe and last but not least, get the changes back to
> us so it can be integreated into our repo.

But just to be clear on the expectations: a patch of the kind in
the first mail which mixes simple (though maybe ugly) renaming with
very complex and/or dubious changes likely to break something will
probably rejected without much further thought (or even just ignored).
On the other hand, splitting the main() function is highly welcome,
and quite a bit of work has been done in the past - though even
that would better be done one step at a time.

> BTW: having MPlayer as a library would be a possible solution
> to our long outstanding GUI problem.

Huh? Our "GUI problem" is that we have an incredibly badly coded
include GUI nobody cares to maintain, I do not see a libmplayer
changing that.
Neither do I see it solve the problems that e.g. smplayer has due
to the official GUI interface (aka slave mode) not being
well-maintained.
Personally, I find it very funny how there are people who praise
the approach of some web browsers to use many different processes
as the greatest thing since whenever while here we mostly get
people complaining about having to launch a separate process (and yes
having both available of course would be nicest, I just wonder who
will keep them working, not even speaking of API/ABI issues).



More information about the MPlayer-dev-eng mailing list