multimedia meeting agenda

[koos vriezen]

2006/5/5, Matthias Kretz <kretz at kde.org>:
> On Tuesday, 2. May 2006 23:16, koos vriezen wrote:
> > On TOn Tuesday 25 April 2006 6:00 am, Matthias Kretz wrote:

> quoting your comment on the dot:
> > What is the idea with the central configuration and choosing the right
> > backend. I can imagine that depending on a certain use, eg. local playback
> > vs. web movies, one would like to choose for an different one. Or can/should
> > a movie player query all backends and let the user decide?
>
> I will test whether having multiple backends available at the same time works
> as soon as we have a few more (working) backends. Until then I believe that
> allowing it will create more problems than it will solve.

But somehow with multible backends, one should be set as default. So
if phonon would include an API for setting the default, instead of
having an included private config dialog, then that would be enough.

> > Who is handling network streaming for eg. mms and rtsp protocols, is that
> > phonon or should the backends handle those (and what happens with password
> > protected links then)?
>
> The URL is handed to the backend via the MediaObject setUrl function. If that
> doesn't work, the MediaObject frontend object will request a ByteStream
> interface and try to open the URL using KIO. This way all KIO URLs will work
> automatically.
> Password protected links is a good question. Probably the best would be for
> the backend to use the KDE facilities to query for the password. If Phonon
> falls back to KIO we have no problem anyway.

Only if it's a mms protocol or so. Maybe add a signal to the api, when
emit'ed the mm application should present some passwd dialog. In case
of an embedded player in konqueror, this passwd can already be known.

> > Is there a way to specify whether the backends should be in- or out-process,
> > eg. for konqueror web browsing one might not want to pull in the gstreamer
> > libs but for a movie player that might not be an issue.
>
> Interesting thought. For those cases where you want to have it out-of-process
> it could really be the best choice to create a phononplayer that gets
> embedded into Konqueror (or whatever app). On the other hand adding a proxy
> interface to make backends out-of-process on the phonon lib level is also
> possible (even after KDE 4.0 is released and Phonon has to stay BC). But I'm
> not convinced that we really want to have that. I'd rather go with the
> embedded phononplayer solution...

Ok, lets hope a phononplayer does well on start-up performance. Eg. I
hope you will use signals for notification rather than presenting own
popup dialogs .. or at least have it in an separate library.

Thanks,
Koos