[MPlayer-G2-dev] Re: G2 CLI/GUI

[D Richard Felker III]

On Tue, May 13, 2003 at 12:25:12AM +0300, Andriy N. Gritsenko wrote:
>     Hi, D Richard Felker III!
> 
> Sometime (on Tuesday, May 13 at  0:02) I've received something...
> >On Mon, May 12, 2003 at 10:23:59PM +0300, Andriy N. Gritsenko wrote:
> >> >> did it because I hoped it will start loadable modules support in G2. Do
> >> >> you against of loadable modules concept at all? If you do then I could
> 
> >> >no
> >> >but i'm against load-all-modules-at-startup concept
> 
> >>     I'm also! :)  But may be anyway we have to scan all available modules
> >> at startup (don't load but check) - I don't think if check only by file
> >> name is enough.
> 
> >Not acceptable. This sort of bloated slow startup nonsense is what I
> >expect from stuff like mozilla and gimp, not mplayer!
> 
>     I didn't say if we have do that scan by loading these plugins. There
> is other way - to create /usr[/local]/lib/mplayer/{ctl,vo,vf} subdirs and
> put plugins of each type there. Plugins names will be name.so - it may be
> enough but version and validity check (and getting all plugin info) will
> be on loading on demand only. Is it ok?

Don't open and validate it, and only even list the files if the user
is using a gui that needs to show a list of plugins. If I'm using
mplayer from the command line, there's absolutely no reason it needs
to know about any drivers/filters/codecs/etc. I'm not actually
specifying on the command line. Checking them is just a waste of time.
Stuff can fail later if the user specifies a plugin that doesn't
actually exist, or a version mismatch occurs, etc., *** when it comes
time to actually load it!! ***

Rich