Trolltech announced today that the Phonon backends, which they have been developing for inclusion in Qt, are being transferred into the KDE source code repository. Phonon is the KDE 4 API for multimedia and is also set to be part of Qt 4.4, scheduled for the end of Q1 2008. You heard it right folks, a part of Qt will be officially hosted and developed inside KDE's very own Subversion repository, from whose loins Phonon first sprung, and be freely available to all under the LGPL.
The code being transferred is: Trolltech's GStreamer Phonon backend for Linux and UNIX platforms, their DirectShow 9 backend for Windows, as well as their Quicktime 7 backend for Mac OS X. All future development on these backends, as well as future development by Trolltech on Phonon itself, will take place directly in the KDE Subversion repository.
Quoting from the press release:
"By developing Phonon components within the globally accessible public KDE source repository, Phonon developers are able to watch and participate in the development of Trolltech's Phonon back-end code and library code contributions. This also allows the community to evaluate and provide input into the work being done by Trolltech’s internal development team. KDE, in turn, benefits by having Trolltech's employed developers contribute to the ongoing development and maintenance of Phonon, freeing KDE developers to work on other aspects of the desktop. This is a marked change from how open source libraries are usually integrated into commercial products, which has typically involved pulling snapshots of the open source code into the commercial product. Additionally, the Windows and Mac OS X backends will enable KDE4 applications running on these platforms to include multimedia functionality."
This is a great move by Trolltech and shows that it "gets" the benefits of collaboration between open source projects and industry. Let's hope that this trend continues in the future.
This is a great move by trolltech.
Does anyone know if this will be in KDE-4.0?
And does this mean that in the future since Qt already has phonon that although Phonon will be developped in KDE's subversion KDE will not release Phonon anymore?
And does someone know in which Qt module (QtGui, etc) Phonon will be or if it will be a new module?
Thanks in advance for any answers :)
For more informations :
Well, since the backends are in /trunk/KDE/kdebase I think they will be included in kde 4.0 :)
Well the ones for the current OS anyway, I don't think KDE on Linux will require a windows phonon backend
Bonus geek points to someone who figures out how to use the Windows phonon backend with winelib on linux.
> Does anyone know if this will be in KDE-4.0?
It already *is*. See http://websvn.kde.org/trunk/KDE/kdebase/runtime/phonon/ and http://websvn.kde.org/?view=rev&revision=747964
> And does this mean that in the future since Qt already has phonon that
> although Phonon will be developped in KDE's subversion KDE will not release
> Phonon anymore?
Sorry, I don't understand what you mean.
But what can tell you is this: Phonon will be released along with each Qt release and each KDE release. This means we'll alternate version numbers.
What could be a source of problems is if you have two sets of headers installed in your system. That could cause compiling errors. If that's the case, you can just disable the compilation of Phonon in Qt or in KDE.
> And does someone know in which Qt module (QtGui, etc) Phonon will be or if
> it will be a new module?
New module called "phonon". It's the exact same API as the one we have in KDE, so no surprises there.
Phonon should be available in tonight's snapshots of Qt 4.4.0.
I see the benefits, but find it confusing. Take PyQT. Will QT's phonon be included in PyQT binding's and if so, will PyQT stay only dependent on QT? (hope so). Same question for PyKDE. The library separation must stay clear. Will there be a QT component _and_ a KDE variant based on it? (both residing in KDE's repository?)
It's the same library. It's just going to get released more often (possibly with minor or no changes between KDE and Qt releases, we'll see). As for dependencies: libphonon itself depends only on Qt libraries. So PyQt could (from the Qt 4.4 release on) contain the Phonon bindings.
Phonon is the same library. It doesn't matter where it comes from, does it?
Presumably what it means is that Phonon will be in KDE only, until Qt4.4 is released and KDE moves to using it. At that point, Phonon will be will be available at a lower layer, in Qt. The only really KDEuser-visible advantage is that the few non-KDE, Qt-only apps that don't use the rest of the KDE libraries will also have good multimedia support. As KDE becomes more and more cross-platform, I'm hoping there will be less and less Qt-only apps anyway, though.
It means paid developers working on Phonon, less maintenance burden for KDE developers, commercial support available for Phonon. Trolltech's work on Phonon will assure good multimedia support on _all_ platforms for KDE.
Congratulations to everyone involved on this great piece of collaboration!
I was under the impression the paid development was happening already, it just moved from Trolltech's repository to KDEs. Am I missing something?
I also noticed the (new style?) KDE description at the end of the title. I really like this one:
KDE is an international technology team that creates integrated Free/Open Source Software for desktop and portable computing. Among KDE's products are a modern desktop system for Linux and UNIX platforms, comprehensive office productivity and groupware suites and hundreds of software titles in many categories including Internet and web applications, multimedia, entertainment, educational, graphics and software development. Building on the cross-platform capabilities of Trolltech®'s Qt®, KDE4's full-featured applications run natively on Linux, BSD, Solaris, Windows and Mac OS X.
It puts the "team" (aka community) in front, and defines the achievements really well. :-)
Thanks, we do too. A slightly modified version of that text will be used in the foreseeable future for About KDE boilerplate text.
"Let's hope that this trend continues in the future."
look at www.heise.de/newsticker/meldung/100517:
"Lars Knoll, die treibende Kraft hinter der Render-Engine KHTML des KDE-Browsers Konqueror, wird Entwicklungsleiter (Vice President of Engineering) beim norwegischen Software-Unternehmen Trolltech. [...]"
This means that Lars Knoll will work for Trolltech as a Vice Predident of Engineering.
For the announcement in English:
For those confused: Lars has been working for Trolltech for 7 years now. The news is that he's now in a new phase of his life, as VP of Engineering. But, even though he's a VP now, he's still getting his hands dirty and coding. Last I saw him, he was deep in discussion about WebKit internals. ;-)
Konqueror is the first of the three killerfeatures of KDE. Then comes Kontact and last but not least Knotes. Because Knotes is one of those convenient little things that make life easier.
I like the knotes plasmoid. I mostly use ti to write little notes for my wife and she to me or simple remind each other of important things. It's very convenient and nice.
That's very cool!
Hey, very cool! Thats on in the eye for all the knockers and doubters :-)
I presume this also means that there is an easily-accessed open repository with examples for other people wanting to write other back-ends as well.
there's nothing easier to access than kdebase, is there? =)
This go for all those "This phonon-thing suxx cause it's not using directly Gstreamer"
but i want nmm!
(_really not to be taken seriously;
have you ever seen the code of that *shudder* )