With Phonon, KDE developers will be able to write applications with multimedia functionality in a fraction of the time needed with one of the above mentioned media frameworks and libraries. This will facilitate the usage of media capabilities in the KDE desktop and applications.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-11-14
that's bull. Phonon is a KDE interface to prevent KDE apps from having to depend on unstable API's and ABI's
That's bull too. I thought Phonon was about protecting KDE from having to keep a buggy or obsolete sound framework.
Excuse me to make you remember that as long as Phonon is depending on unstable API and ABI, it won't solve anything for KDE.
if gstreamer would commit to staying stable during the whole KDE 4 series, AND could give garantuee they'll continue to be the best, KDE could use it
This is not the goal of GStreamer at all. And I wonder how an app can be guaranteed to stay the best.
GStreamer is the best currently, because it is the only one of its kind on Linux.
Phonon can garantee API and ABI stabillity, and as you can choose the backend, it'll always be the best
I wonder. As you can't guarantee to support all features of the backend, and as Phonon still depends on the backends, API and ABI stability means very reduced features.
Member since:2005-07-06
> I thought Phonon was about protecting KDE from
> having to keep a buggy or obsolete sound framework.
sometimes a good solution fixes several problems all at once. phonon is a good example of this.
> As you can't guarantee to support all features of
> the backend, and as Phonon still depends on the
> backends, API and ABI stability means very reduced
> features.
as a generic statement this makes sense. as a statement about multimedia as used in 99% of desktop apps it doesn't.
think about what 99% of desktop applications need to do with media. open a uri, get some information on the media (e.g. metadata), play, seek, pause, stop, record, apply affects if available ... it's pretty basic and at this point in time rather well defined.
if we go to non-linear video editors or studio quality sound recording rigs, then phonon may not meet their needs and the developers of those apps may find the need to write directly to a media engine (or even OS-specific API).
but for 99% of apps it's a well contained problem space that is 100% covered by 100% of non-laughable media stacks.
this is a good example of when thinking specifically (e.g. "about multimedia and desktop applications") versus generically (e.g. "programming design patterns") is helpful.
Member since:
2005-07-07
that's bull. Phonon is a KDE interface to prevent KDE apps from having to depend on unstable API's and ABI's. if gstreamer would commit to staying stable during the whole KDE 4 series, AND could give garantuee they'll continue to be the best, KDE could use it. Phonon can garantee API and ABI stabillity, and as you can choose the backend, it'll always be the best.