[MPlayer-DOCS] CVS: homepage/essays/src interview-Arpi.src.en, 1.5, 1.6 interview-Gabucino.src.en, 1.5, 1.6 interview-Pontscho.src.en, 1.5, 1.6
Diego Biurrun CVS
syncmail at mplayerhq.hu
Sat May 14 16:55:48 CEST 2005
CVS change done by Diego Biurrun CVS
Update of /cvsroot/mplayer/homepage/essays/src
In directory mail:/var2/tmp/cvs-serv19737/essays/src
Modified Files:
interview-Arpi.src.en interview-Gabucino.src.en
interview-Pontscho.src.en
Log Message:
indentation cosmetics
Index: interview-Arpi.src.en
===================================================================
RCS file: /cvsroot/mplayer/homepage/essays/src/interview-Arpi.src.en,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- interview-Arpi.src.en 14 May 2005 14:51:54 -0000 1.5
+++ interview-Arpi.src.en 14 May 2005 14:55:45 -0000 1.6
@@ -15,14 +15,14 @@
<p>
I've already written numerous articles on
- this site about MPlayer. In one of them I claimed it's the fastest, most
- usable MOVIE player for Linux/Unix. It's also famous, known in every single
- corner of the world (not joking). In my latest article I also wrote that
- - according to me - more people know it abroad than in Hungary. I think
- we Hungarians should be proud of the projects which gain us fame all around
- the globe. Thus I decided to make an interview with the creator and main
- programmer of MPlayer, Árpád Gereöffy (A'rpi). I've asked him about
- quite some topics: GPL, MPlayer's history, development, etc.
+this site about MPlayer. In one of them I claimed it's the fastest, most
+usable MOVIE player for Linux/Unix. It's also famous, known in every single
+corner of the world (not joking). In my latest article I also wrote that
+- according to me - more people know it abroad than in Hungary. I think
+we Hungarians should be proud of the projects which gain us fame all around
+the globe. Thus I decided to make an interview with the creator and main
+programmer of MPlayer, Árpád Gereöffy (A'rpi). I've asked him about
+quite some topics: GPL, MPlayer's history, development, etc.
</p>
<p>
@@ -33,41 +33,41 @@
<dt>UP:</dt>
<dd>When did you start programming? Where did the
- idea to write a MOVIE player come from?</dd>
+idea to write a MOVIE player come from?</dd>
<dt>A'rpi:</dt>
<dd>These are two questions :)
<ol>
<li>Well that was a long time ago, at my age of 10, on c64 :). (Like Pontscho,
- but he had vic20). I've got bored with the games quickly, and started to
- write miscellaneous things, of course not big stuff like MPlayer... I've
- been unsatisfied with ready things even at that time, and wanted to rewrite
- everything. After all, this is what keeps Linux alive, and evolving. Everyone
- touches into the programs, which in turn gets better.</li>
+ but he had vic20). I've got bored with the games quickly, and started to
+ write miscellaneous things, of course not big stuff like MPlayer... I've
+ been unsatisfied with ready things even at that time, and wanted to rewrite
+ everything. After all, this is what keeps Linux alive, and evolving. Everyone
+ touches into the programs, which in turn gets better.</li>
<li>The idea came a year ago. Somebody lent me a VCD, and - needless to say -,
- neither of the current players could cope with it. I wasn't satisfied with
- mpegtv anyways, and that was the only working mpeg player available at that
- time. So I stayed with the well-working method: let's rewrite one :) My
- victim was XMPS, I've spent a lot of time (1 week :)) fixing bugs, and at
- the end I realized that the codec (SMPEG) was bad, so all is in vain.
- Plan "B": let's write one. You know what happened :)</li>
+ neither of the current players could cope with it. I wasn't satisfied with
+ mpegtv anyways, and that was the only working mpeg player available at that
+ time. So I stayed with the well-working method: let's rewrite one :) My
+ victim was XMPS, I've spent a lot of time (1 week :)) fixing bugs, and at
+ the end I realized that the codec (SMPEG) was bad, so all is in vain.
+ Plan "B": let's write one. You know what happened :)</li>
</ol>
</dd>
<dt>UP:</dt>
<dd>Who develops MPlayer? Who are the team members, and what
- their tasks are?</dd>
+their tasks are?</dd>
<dt>A'rpi:</dt>
<dd>Well that's a complicated question. As with the opensource
- projects in general, this one also has much (several hundred!) developers,
- most of them submit only few line fixes, but those are also very helpful!
- I would split the "team" to 3 parts: core members - this is their main
- project, spending most of their free time on MPlayer, the contributors who
- send patches, developing smaller parts of the code, and the "outsiders"
- who don't have anything to do with MPlayer, but write libs which we use,
- and which are essential in out progress. The developers' list is available
- in the documentation, so I'd just outline the most active core members here:
+projects in general, this one also has much (several hundred!) developers,
+most of them submit only few line fixes, but those are also very helpful!
+I would split the "team" to 3 parts: core members - this is their main
+project, spending most of their free time on MPlayer, the contributors who
+send patches, developing smaller parts of the code, and the "outsiders"
+who don't have anything to do with MPlayer, but write libs which we use,
+and which are essential in out progress. The developers' list is available
+in the documentation, so I'd just outline the most active core members here:
<ul>
<li>Gabucino - documentation and homepage maintainer and translator, user-whacker,
IRC admin, morale decreaser, and the winner of the face compo, btw :)</li>
@@ -102,17 +102,17 @@
<dt>A'rpi:</dt>
<dd>Well a year ago my answer would just be: this one works. This
- one year was very active in linux multimedia, a lot of players have born
- from nearly nothing, and then disappeared according to the laws of the
- evolution. Either of he players still actively maintained are good, but
- each of them has its bias on different things. The speciality of MPlayer
- is running in one process. Many people think this is a Bad Thing, but they
- can't deny that it works, and gives greater performance than the concurrent
- players, like xine of avifile. Also the audio & video synchronizing code is
- special, when I coded this, neither of the current players cared about it.
- This has changed now, but bugreports like "the audio was synced only with
- MPlayer" are frequent even now. Nowadays we grew above the other players
- in supported platforms, output devices, and fileformats.
+one year was very active in linux multimedia, a lot of players have born
+from nearly nothing, and then disappeared according to the laws of the
+evolution. Either of he players still actively maintained are good, but
+each of them has its bias on different things. The speciality of MPlayer
+is running in one process. Many people think this is a Bad Thing, but they
+can't deny that it works, and gives greater performance than the concurrent
+players, like xine of avifile. Also the audio & video synchronizing code is
+special, when I coded this, neither of the current players cared about it.
+This has changed now, but bugreports like "the audio was synced only with
+MPlayer" are frequent even now. Nowadays we grew above the other players
+in supported platforms, output devices, and fileformats.
</dd>
<dt>UP:</dt>
Index: interview-Gabucino.src.en
===================================================================
RCS file: /cvsroot/mplayer/homepage/essays/src/interview-Gabucino.src.en,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- interview-Gabucino.src.en 14 May 2005 14:51:54 -0000 1.5
+++ interview-Gabucino.src.en 14 May 2005 14:55:45 -0000 1.6
@@ -43,9 +43,9 @@
<dt>Gabucino:</dt>
<dd>Because the xMach is not ready yet ;) Jokes apart, I'm not
- satisfied with the Linux (though you didn't ask but I use LFS), the last
- "stable" kernel was the 2.4.9 for me, pity it has secholes.. I have restrains
- for a system which developers think gcc 2.96 an useful thing.. (Linus, Cox)
+satisfied with the Linux (though you didn't ask but I use LFS), the last
+"stable" kernel was the 2.4.9 for me, pity it has secholes.. I have restrains
+for a system which developers think gcc 2.96 an useful thing.. (Linus, Cox)
</dd>
@@ -54,9 +54,9 @@
<dt>Gabucino:</dt>
<dd>I've been using the avifile 0.49 at that time, and I noticed that
- arpi guy constantly mailing on its list (and on 3 other lists too), so I
- though I'd take a look at that MPlayer he's coding.. Then I reported bugs,
- afterwards it's history ;)</dd>
+arpi guy constantly mailing on its list (and on 3 other lists too), so I
+though I'd take a look at that MPlayer he's coding.. Then I reported bugs,
+afterwards it's history ;)</dd>
<dt>trey:</dt>
<dd>When did you join the MPlayer project?</dd>
@@ -66,105 +66,105 @@
<dt>trey:</dt>
<dd>How does the development happen? Could you tell about an average day
- when you all work actively?</dd>
+when you all work actively?</dd>
<dt>Gabucino:</dt>
<dd>Hard to answer this question, because it depends. If we're thinking
- about "inner" (hungarian) developers and their doings, that's talked about
- on the IRC. And reversed in CVS ;) Other developers are sending patches
- on the dev-eng list, where A'rpi verifies/criticizes/forgets/commits them
- (the latter is rare;) .. And I wrote the documentation for them.</dd>
+about "inner" (hungarian) developers and their doings, that's talked about
+on the IRC. And reversed in CVS ;) Other developers are sending patches
+on the dev-eng list, where A'rpi verifies/criticizes/forgets/commits them
+(the latter is rare;) .. And I wrote the documentation for them.</dd>
<dt>trey:</dt>
<dd>You write the documentation of MPlayer. How are these pages made?
- Obviously you have to know everything about the technical details so
- good man pages and tutorials will be made.</dd>
+Obviously you have to know everything about the technical details so
+good man pages and tutorials will be made.</dd>
<dt>Gabucino:</dt>
<dd>I have to know about the workings, the structure of MPlayer, I mean
- the connectivity of its parts (I won't write sentences like this ever again;).
- Anyway everything just comes out by itself.. The documentation is made with
- joe :) No special technique, I usually write my ideas on a TODO list, and
- when I get bored I document them all. Exceptions from this rule are the
- important changes, and those few days before release, when even the irclog's
- size increases dramatically ;) And the rereading of the dox (well, should
- be;), etc..</dd>
+the connectivity of its parts (I won't write sentences like this ever again;).
+Anyway everything just comes out by itself.. The documentation is made with
+joe :) No special technique, I usually write my ideas on a TODO list, and
+when I get bored I document them all. Exceptions from this rule are the
+important changes, and those few days before release, when even the irclog's
+size increases dramatically ;) And the rereading of the dox (well, should
+be;), etc..</dd>
<dt>trey:</dt>
<dd>The documentation is well-written, usable. But I think there's too much
- RTFM inside, and its style is belittling sometimes. What's your opinion
- about this?</dd>
+RTFM inside, and its style is belittling sometimes. What's your opinion
+about this?</dd>
<dt>Gabucino:</dt>
<dd>Dirty accusation :) Well it was a bit freestyle some time ago,
- but it has changed since. Anybody spreading this has never RTFMed :)</dd>
+but it has changed since. Anybody spreading this has never RTFMed :)</dd>
<dt>trey:</dt>
<dd>Last year Barr's article caused a major uproar. He talked belittling
- about MPlayer's documentation, etc. How did you feel about this?</dd>
+about MPlayer's documentation, etc. How did you feel about this?</dd>
<dt>Gabucino:</dt>
<dd>Bad. I hate when I see I'm right, and there ARE many lame Linux
- users.. Like me ;))</dd>
+users.. Like me ;))</dd>
<dt>trey:</dt>
<dd>Did it cast back you in you work? And the others?</dd>
<dt>Gabucino:</dt>
<dd>It took us time to flame on the lists ;) Anyway nobody cared more
- than this.</dd>
+than this.</dd>
<dt>trey:</dt>
<dd>I've already asked Pontscho this, but what is the reason for this
- silence around MPlayer? He said there'll be a release. When will this
- occur exactly? Is it going to be some big version number change?</dd>
+silence around MPlayer? He said there'll be a release. When will this
+occur exactly? Is it going to be some big version number change?</dd>
<dt>Gabucino:</dt>
<dd>Yes, probably it'll be 1.0, but surely a big step. When? Well
- looking at the great number of bugreports, it won't be ready until Apr 1st :)
- Unfortunately. Anyway the reason is that there have been numerous large
- changes in the code lately, and we have to fix their consequences.</dd>
+looking at the great number of bugreports, it won't be ready until Apr 1st :)
+Unfortunately. Anyway the reason is that there have been numerous large
+changes in the code lately, and we have to fix their consequences.</dd>
<dt>trey:</dt>
<dd>A few days ago Nick Kurshev has forked, and started a new project
- called MPlayerXP. What were the reasons for his decision? Won't this cast
- MPlayer's development back?</dd>
+called MPlayerXP. What were the reasons for his decision? Won't this cast
+MPlayer's development back?</dd>
<dt>Gabucino:</dt>
<dd>Nick went mad :) I think this because he became GPL maniac :)
- It won't cast back IMHO. See the next question.</dd>
+It won't cast back IMHO. See the next question.</dd>
<dt>trey:</dt>
<dd>The strenght of the MPlayer is being not multithreaded. It's unique by
- running on one thread. What is the meaning of this?</dd>
+running on one thread. What is the meaning of this?</dd>
<dt>Gabucino:</dt>
<dd>It runs on one thread :) man ps :) I mean if you take a look at it,
- you see only 1 mplayer process, not 20. Like xine, I've just read their list,
- even pointing over a GUI button spawns a new process (thread:) And it
- forgets to kill it currently :) So every player runs on multiple threads BUT
- MPlayer. And we all know which one is more stable. (of course this is
- demagogy, but it's true :)</dd>
+you see only 1 mplayer process, not 20. Like xine, I've just read their list,
+even pointing over a GUI button spawns a new process (thread:) And it
+forgets to kill it currently :) So every player runs on multiple threads BUT
+MPlayer. And we all know which one is more stable. (of course this is
+demagogy, but it's true :)</dd>
<dt>trey:</dt>
<dd>According to a mail of Kurshev, if A'rpi accepts his ideas, he's
- willing to rejoin the MPlayer team, and will help to make the NO.1 movie
- player on the earth. Do you see any chance for this?</dd>
+willing to rejoin the MPlayer team, and will help to make the NO.1 movie
+player on the earth. Do you see any chance for this?</dd>
<dt>Gabucino:</dt>
<dd>No. Anyways I tried to test MPlayerXP, but it didn't compile :) And
- as I said, MPlayer already plays everything on this lousy K6/2-500, DVD, DivX,
- all.</dd>
+as I said, MPlayer already plays everything on this lousy K6/2-500, DVD, DivX,
+all.</dd>
<dt>trey:</dt>
<dd>What do you think could be improved in MPlayer?</dd>
<dt>Gabucino:</dt>
<dd>I asked the very same question from myself at every release,
- I won't do it again :) Anyway the direct render is complete, and is deadly..
- Practically even a 300Mhz K6 will be enough instead of an 500Mhz. I mean,
- as soon as the libavcodec supports it. So MPlayer is the god! Give 110% of
- your tax to MPlayer's underpaid coders, doxwriters! Etc etc.. ;)</dd>
+I won't do it again :) Anyway the direct render is complete, and is deadly..
+Practically even a 300Mhz K6 will be enough instead of an 500Mhz. I mean,
+as soon as the libavcodec supports it. So MPlayer is the god! Give 110% of
+your tax to MPlayer's underpaid coders, doxwriters! Etc etc.. ;)</dd>
<dt>trey:</dt>
<dd>Do you work on other projects, or only on MPlayer?</dd>
@@ -174,42 +174,42 @@
<dt>trey:</dt>
<dd>A few months ago the design of your homepages changed. Many think the
- previous was better. Do you like the current one?</dd>
+previous was better. Do you like the current one?</dd>
<dt>Gabucino:</dt>
<dd>I do :) Anyway the best was my (oooold) design, it's a pity noone
- liked that except me :) BTW the new design is ready, but we'll wait for
- the release (as always).</dd>
+liked that except me :) BTW the new design is ready, but we'll wait for
+the release (as always).</dd>
<dt>trey:</dt>
<dd>If you check movie players on Linux, which one do you think is
- worth mentioning, or contains neat stuff?</dd>
+worth mentioning, or contains neat stuff?</dd>
<dt>Gabucino:</dt>
<dd>There's that MPlayerXP, and it contains that whaddyacallit player..
- Ah, MPlayer! Pity they modified it :))</dd>
+Ah, MPlayer! Pity they modified it :))</dd>
<dt>trey:</dt>
<dd>Do you keep an eye on other players' features? Do you have rivals?
- I mean, when XYPlayer implements "halfballeffect-accelerator-turboenhancement",
- do you hurry to implement the same thing?</dd>
+I mean, when XYPlayer implements "halfballeffect-accelerator-turboenhancement",
+do you hurry to implement the same thing?</dd>
<dt>Gabucino:</dt>
<dd>We keep an eye on what is xine just steal^H^H^H^H^Hporting from us ;))
- Also due of MPlayer being non-GPL, and xine is.. Anyway I couldn't tell any
- feature we ported from them since their directshow loader code in C. And
- that was pretty long ago ;)</dd>
+Also due of MPlayer being non-GPL, and xine is.. Anyway I couldn't tell any
+feature we ported from them since their directshow loader code in C. And
+that was pretty long ago ;)</dd>
<dt>trey:</dt>
<dd>Many people asked if there'll be a Windows port of MPlayer. What's the
- status?</dd>
+status?</dd>
<dt>Gabucino:</dt>
<dd>"Will be"?? It WAS! :) Anyway I think it's compilable on windowz,
- though probably not easy, and Vidix doesn't run on it yet. But the last
- thing I'd think of would be flashing big text proclaiming a vindoz port,
- InstallShield exe, etc.. After all, what could we boast to the
- winnyozusers then? ;)</dd>
+though probably not easy, and Vidix doesn't run on it yet. But the last
+thing I'd think of would be flashing big text proclaiming a vindoz port,
+InstallShield exe, etc.. After all, what could we boast to the
+winnyozusers then? ;)</dd>
<dt>trey:</dt>
<dd>What are your other tasks in the project, apart documentation writing?</dd>
@@ -222,32 +222,32 @@
<dt>Gabucino:</dt>
<dd>You can read about it in the dev-eng archives :) Anyway nothing
- special, he just felt I don't update the doc regularly.</dd>
+special, he just felt I don't update the doc regularly.</dd>
<dt>trey:</dt>
<dd>You seem to be having some problems with linux lately =). What's the
- problem with it?</dd>
+problem with it?</dd>
<dt>Gabucino:</dt>
<dd>I could answer your second question in loong sentences (I won't:),
- but I don't understand who's spreading rumors about me? :)</dd>
+but I don't understand who's spreading rumors about me? :)</dd>
<dt>trey:</dt>
<dd>What tools do you use when you work (hardware, software)?</dd>
<dt>Gabucino:</dt>
<dd>386, because its LCD is nice (better than this 10 years old 14" :),
- joe on eterm because joe rulez, and eterm is transparent, and windowmaker
- because it's godly.</dd>
+joe on eterm because joe rulez, and eterm is transparent, and windowmaker
+because it's godly.</dd>
<dt>trey:</dt>
<dd>I've read on mplayer-dev-eng about you want to convert the documentation
- into another format. There was a little disagreement about that. Care to
- explain?</dd>
+into another format. There was a little disagreement about that. Care to
+explain?</dd>
<dt>Gabucino:</dt>
<dd>There wasn't. :) It'll be converted to SGML, that's sure. It also
- fits the plebs' needs. :)</dd>
+fits the plebs' needs. :)</dd>
<dt>trey:</dt>
<dd>What do you do apart MPlayer?</dd>
@@ -265,23 +265,23 @@
<dt>trey:</dt>
<dd>A few days ago A'rpi complained that you rarely maintain the
- documentation, and he's searching for new co- or maintainer for this
- task. There were several mails about this. How are the things now?</dd>
+documentation, and he's searching for new co- or maintainer for this
+task. There were several mails about this. How are the things now?</dd>
<dt>Gabucino:</dt>
<dd>I though of quitting, then I realized that A'rpi is not the
- targeted reader community, and the users never complained.</dd>
+targeted reader community, and the users never complained.</dd>
<dt>trey:</dt>
<dd>For an outsider it the MPlayer project would seem to be falling apart.
- Am I mistaken?</dd>
+Am I mistaken?</dd>
<dt>Gabucino:</dt>
<dd>That's also my opinion. Anyway don't feel sorry for Nick, he'll
- want to come back :) Unfortunately, lately A'rpi has been flaming people more
- than usual.. Like me, though he should know that it's futile to flame against
- me ;) In any case, let's hope direct render will be ready before he gets
- nerve breakdown ;)</dd>
+want to come back :) Unfortunately, lately A'rpi has been flaming people more
+than usual.. Like me, though he should know that it's futile to flame against
+me ;) In any case, let's hope direct render will be ready before he gets
+nerve breakdown ;)</dd>
</dl>
Index: interview-Pontscho.src.en
===================================================================
RCS file: /cvsroot/mplayer/homepage/essays/src/interview-Pontscho.src.en,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- interview-Pontscho.src.en 14 May 2005 14:51:54 -0000 1.5
+++ interview-Pontscho.src.en 14 May 2005 14:55:45 -0000 1.6
@@ -41,8 +41,8 @@
<dt>Pontscho:</dt>
<dd>I loved hacking things at that time. Nowadays I'm bored with the
- continuous messing to make for example an ISDN modem working. I've stayed
- with it for the stability (although the strangest things occur sometims ...).
+continuous messing to make for example an ISDN modem working. I've stayed
+with it for the stability (although the strangest things occur sometims ...).
And because I can work on cross-platforms.</dd>
<dt>trey:</dt>
@@ -66,11 +66,11 @@
<dt>Pontscho:</dt>
<dd>That's stupid. Everything is present for a good demo. However, those
- "compatible" window managers really gives us a hard time. There are bunch
- of JPEG loaders, sound systems are available, and also hell-a-lot of HW
- accelerated OpenGL is available. It's just that Linux desktop isn't really
- frequent on the scene. Maybe I could count on one hand how many teams
- publish Linux demo/intros. We'd like to change this, theoretically the new
+"compatible" window managers really gives us a hard time. There are bunch
+of JPEG loaders, sound systems are available, and also hell-a-lot of HW
+accelerated OpenGL is available. It's just that Linux desktop isn't really
+frequent on the scene. Maybe I could count on one hand how many teams
+publish Linux demo/intros. We'd like to change this, theoretically the new
Fresh3D engine will have Linux support.
<br>
BTW A'rpi is a member of the Astral team, they code their demos primarily under
@@ -81,11 +81,11 @@
<dt>Pontscho:</dt>
<dd>Hm. Yes, but they don't run under Linux, The FPC's X compatibility is
- nil, the gcc compiled objects' linkability is beneath all criticism. Not
- under Linux. Under Win32. So it's very hard to work under crossplatform
- with it. Under Win32, there's the 54 series in which I've participated.
- (Konplex54, Synbolik54, Konputer 54, 54). And I had a party winner 4k
- some years ago. (Written in dosemu :) I'd like to port Konplex54 to Linux,
+nil, the gcc compiled objects' linkability is beneath all criticism. Not
+under Linux. Under Win32. So it's very hard to work under crossplatform
+with it. Under Win32, there's the 54 series in which I've participated.
+(Konplex54, Synbolik54, Konputer 54, 54). And I had a party winner 4k
+some years ago. (Written in dosemu :) I'd like to port Konplex54 to Linux,
amongst all Fresh stuff I like that one the most.</dd>
<dt>trey:</dt>
@@ -93,10 +93,10 @@
<dt>Pontscho:</dt>
<dd>As I recall, in 2000, on the Conference7007 (a party), A'rpi told
- me he wrote an mpeg1 decoder in 5k with hardware acceleration. I asked him
- to send it to me, then we argued it's fscking slow. And it segfaults, etc.
- Then I realized I was at fault because I didn't RTFM, and the binary was
- optimized to i686, and I had a k6/2. And they don't like each other. So
+me he wrote an mpeg1 decoder in 5k with hardware acceleration. I asked him
+to send it to me, then we argued it's fscking slow. And it segfaults, etc.
+Then I realized I was at fault because I didn't RTFM, and the binary was
+optimized to i686, and I had a k6/2. And they don't like each other. So
the first version on the configure script was written...</dd>
<dt>trey:</dt>
@@ -111,11 +111,11 @@
<dt>Pontscho:</dt>
<dd>I have a 450 at 500 AMD K6/2 with a Matrox G400, for years. Tuner card,
- Vortex2, GUS PnP (does anyone remember what is it?:) 384 MB RAM, DVD, stuff
- like that. This is what I usually use, and it performs very well. For
- example I can watch any DVD movie I'd like to. Apropo... If someone has a
- DVD that he grew bored of, please send, because I don't have such, thus
- the GUI's DVD support proceeds slowly. :))) Software? DosNavigator, Gimp, gcc
+Vortex2, GUS PnP (does anyone remember what is it?:) 384 MB RAM, DVD, stuff
+like that. This is what I usually use, and it performs very well. For
+example I can watch any DVD movie I'd like to. Apropo... If someone has a
+DVD that he grew bored of, please send, because I don't have such, thus
+the GUI's DVD support proceeds slowly. :))) Software? DosNavigator, Gimp, gcc
xnview :)</dd>
<dt>trey:</dt>
@@ -137,13 +137,13 @@
<dt>Pontscho:</dt>
<dd>I code the graphical user interface for MPlayer. Except for some
- small changed, the whole is my work. The title "master of CVS" is irony.
- Some time ago we and Gabucino (at that time I didn't know anything about CVS)
+small changed, the whole is my work. The title "master of CVS" is irony.
+Some time ago we and Gabucino (at that time I didn't know anything about CVS)
messed up our CVS repository on SourceForge :)</dd>
<dt>trey:</dt>
<dd>Few months ago A'rpi announced he'll just handle the patches and managing
- the CVS from now, since he doesn't have as much free time as he'd want to.
+the CVS from now, since he doesn't have as much free time as he'd want to.
How did this affect the project?</dd>
<dt>Pontscho:</dt>
@@ -151,27 +151,27 @@
<dt>trey:</dt>
<dd>Many think the development of MPlayer has slowed down. There has been
- one release this year (MPlayer 0.60 2002. January 02). I heard there are
- problems with the CVS version, compilation problems, etc. The homepage
+one release this year (MPlayer 0.60 2002. January 02). I heard there are
+problems with the CVS version, compilation problems, etc. The homepage
doesn't change. How do you evaluate this?</dd>
<dt>Pontscho:</dt>
<dd>Gabu has just told he's going to commit right now. He was on strike
- until now. Anyways the development hasn't slowed down, but the current changes
- are unseen to the users. It's hard to see for the end user that A'rpi has
- begun to rewrite the user interface, and also the GUI code was rewritten
+until now. Anyways the development hasn't slowed down, but the current changes
+are unseen to the users. It's hard to see for the end user that A'rpi has
+begun to rewrite the user interface, and also the GUI code was rewritten
some weeks ago.</dd>
<dt>trey:</dt>
<dd>As far as I know binary distribution of MPlayer is forbidden (because of
- speed problems). However I've heard MPlayer's going to be included in the UHU
+speed problems). However I've heard MPlayer's going to be included in the UHU
Linux. How did you solve UHU inclusion? Do you distribute the source?</dd>
<dt>Pontscho:</dt>
<dd>No. Since the UHU team has helped us very much (server, hardware),
- we've mostly overcame the inclusion problem (Don't start celebrating, there
- won't be .deb, .rpm packages for a while). As we have daily contact with them,
- they can solve the inclusion. But there have been numerous arguments about
+we've mostly overcame the inclusion problem (Don't start celebrating, there
+won't be .deb, .rpm packages for a while). As we have daily contact with them,
+they can solve the inclusion. But there have been numerous arguments about
this.</dd>
<dt>trey:</dt>
@@ -180,7 +180,7 @@
<dt>Pontscho:</dt>
<dd>Because we sympathize with their efforts. And despite all the rumors,
- it's going to be good. They've worked hard, and it became useful. It's a fact,
+it's going to be good. They've worked hard, and it became useful. It's a fact,
it's not for servers yet. However it's perfect for desktops.</dd>
<dt>trey:</dt>
@@ -189,9 +189,9 @@
<dt>Pontscho:</dt>
<dd>:))))) I plan to release it on christmas, especially as it still
- needs some development. Oh well. It is going to be an installer for MPlayer.
- In theory it'll be capable of downloading and compiling the source with the
- necessary fonts, skins. But I haven't been able to touch it lately, due to
+needs some development. Oh well. It is going to be an installer for MPlayer.
+In theory it'll be capable of downloading and compiling the source with the
+necessary fonts, skins. But I haven't been able to touch it lately, due to
short free time.</dd>
<dt>trey:</dt>
@@ -207,8 +207,8 @@
<dt>Pontscho:</dt>
<dd>The RedHat just flamed us, however we also had our opinions of them,
- mostly due to gcc 2.96 ;) A hungarian guy contacted us from SuSE, but the
- packability wasn't even as possible as today. (Wow the Godfather has just
+mostly due to gcc 2.96 ;) A hungarian guy contacted us from SuSE, but the
+packability wasn't even as possible as today. (Wow the Godfather has just
stripped his wife:)</dd>
<dt>trey:</dt>
@@ -220,7 +220,7 @@
<dt>trey:</dt>
<dd>There was a little mess with the OS2 MPlayer code. According to you the
- russian guy "stole" the code. What was the outcome? Have you managed to
+russian guy "stole" the code. What was the outcome? Have you managed to
resolve it?</dd>
<dt>Pontscho:</dt>
More information about the MPlayer-DOCS
mailing list