[MPlayer-G2-dev] Re: g2 config - restart...

Arpi arpi at thot.banki.hu
Wed May 14 14:57:31 CEST 2003


Hi,

> Sometime (on Wednesday, May 14 at  0:39) I've received something...
> >(pre-note: Andriy please don't offend Albeu, he seems to understand the
> >actual problems and solutions better than you...)
> 
>     I want to say it in public: Albeu, please, forgive me if I offended
> you, I didn't want to offend you a little, I just wanted to have a good
> config API, it's all.
> 
> >Ok I guess we want to much from the config api.
> >Actually wanting _a_ config api is alreayd too much.
> >Better separate it to layers, like the rest of teh code
> >(stream/demuxer/decoder/filter/ao/vo for example).
> 
> [.....]
> 
> Whole thing is good. But I have some questions to API implementation.
> 
> 1. Where application and UI will have all options tree?

where they store it, probably in memory... :)

> 2. How application or UI will know about all available types of modules?

app/ui author will read g2 framework layout documentation, so he will know
that there are ao, vo, ad, vd, af, vf etc. He already have to know what he
have and what he can use...

> 3. How application or UI/parser will find all available modules of some
>     type?

see layer 1 func 1

> 4. How application or UI/parser will get options of certain module?

see layer 1 func 2

> 5. How open() function will call UI/parser to configure own instance of
>     parameters?

heh?
app/ui/layer3 will call filter's open after called the config parser (layer2).

> 6. How UI/parser can change parameters of certain module in runtime?

control() as you wrote days ago
btw also see iive's draft, it has some nice ideas, esp. around runtime config

> 7. How UI can tell the core to rebuild (insert/delete module instance)
>     filter chain?

see vf.h

> I think, it all must be in API documentation, and API must allow that.

yes
the missunderstanding is only what API
filter insertion/deletion is part of filter api, not config api

> Any UI maker will ask you the same questions. Gui (or any other UI)
> _really_ need all these so we cannot deny it. Don't say, please, we
> should wait to G3 - current G2 can do all this. All we have to do - to
> create API that will allow that. :)

sure

A'rpi / Astral & ESP-team

--
Developer of MPlayer, the Movie Player for Linux - http://www.MPlayerHQ.hu



More information about the MPlayer-G2-dev mailing list