Choosing a Phonon backend

[Fabio Locati]

As I said some time ago, imho phonon have to be able to use in the same time 
more than one backend. When a program ask to phonon a function that is not 
developped in the 'default backend' phonon have to use another backend.
I think that while you are installing the program, the program have to declare 
which backand are supported (ie: e normal audio player can declare that all 
its functions can work with: xine, gstreamer, vlc) and than the installer will 
controll there there is at least one of these. A more complicated program can 
say that he need: (xine or gstreamer or vlc) and NMM, than the installer will 
have to check that all the dependeces are satisfied. IMHO this is the way to 
go.

On Friday 28 March 2008 09:39:27 Aaron J. Seigo wrote:
> On Friday 28 March 2008, Ian Monroe wrote:
> > Plus it's not clear to me why the user should care what backend is
> > being used.
>
> usually they shouldn't and the system should provide sane defaults.
>
> the overall system (e.g. phonon) should be able to guess this best, the
> user might be able to provide some good old fashioned
> human-knows-better-than-the-computer, but the application is probably the
> least equipped to make such decisions. it's also a recipe for subtle
> inconsistencies between apps (where do you set this in FooApp, BarApp, etc)
>
> imho, phonon should orchestrate all of this and the app should stay out of
> the way.
>
> if the use case is, "but my application requires the following N attributes
> from the backend" then maybe phonon needs a way to resolve such requests
> internally. that doesn't require the apps having any say over the actual
> backend selection, however.
>
> > I mean if apps can choose "incompatible mechanisms", which
> > stops the user from doing so?
>
> trial and error, most likely .. and at least this way the settings are in
> one place, not scattered randomly through apps and are gauranteed to be
> configurable versus the well meaning "nope, you're going to use backend
> $FOO with my app" developer.
>
> every time an app requires a given backend, that's a failing in phonon
> imho. the xine backend is a good example of that, and afaik, is being
> addressed.
>
>
> really, all the of the above are pretty basic framework design concepts.


-- 
Fabio Alessandro Locati
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-multimedia/attachments/20080328/809782f3/attachment.sig>
-------------- next part --------------
_______________________________________________
kde-multimedia mailing list
kde-multimedia at kde.org
https://mail.kde.org/mailman/listinfo/kde-multimedia