From kde-multimedia Mon Sep 06 08:14:50 2004 From: Matthias Kretz Date: Mon, 06 Sep 2004 08:14:50 +0000 To: kde-multimedia Subject: Re: summary of the aKademy meetings Message-Id: <200409061014.54876.kretz () kde ! org> X-MARC-Message: https://marc.info/?l=kde-multimedia&m=109445858925689 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============0738437290==" --===============0738437290== Content-Type: multipart/signed; boundary="nextPart1162205.mI65SVBIEn"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart1162205.mI65SVBIEn Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 06 September 2004 05:18, Charles Samuels wrote: > As I figure, the only thing it solves is that it gives us a simple API.=20 > The fact is that it's a bloated simple API because of the plugins. What exactly is bloated about it? The fact that you interface and=20 implementation are separate, and therefor every call to a method has to go= =20 through the virtual table? Or do you mean the backend loading that happens at construction of the=20 =46actory? > As amaroK insists on supporting every system out there, that doesn't > matter. Noatun will require a specific API (probably NMM). > > In other words KDE will eventually require a single API, so this entire > pluggable thing will only result in bloat. But I don't want to force that non-Qt/KDE API on KDE developers. They shoul= d=20 be able to choose what they want. Just to get an overview what the multiple backends give us: =2D Independent from the API/ABI stability of the multimedia Frameworks sin= ce=20 for an incompatible version you can just add a new backend - no code using= =20 kdemm broken. =2D Compatible to KDE 2 and 3: When KDE 4 comes out some people still might= be=20 using aRts apps and therefor might require the aRts backend to be used. =2D Independent from the success of the multimedia Framework we chose. If w= e=20 decide to go for gstreamer only and then MAS becomes the preferred multimed= ia=20 system for Linux we're stuck with gstreamer - just like we have it now with= =20 aRts. =2D I'd guess if we have to decide on the one and only framework now we'd t= ake=20 gst, but then you have those anti-glib fanatics ;-) flaming again because o= f=20 a hard dependence of KDE against glib. (pretty much a moot point) =2D KDE can fit better into different requirements/environments: Users/Admins might want to use some special features of that one multimedia= =20 framework that isn't possible with another framework (yet). I'd like to giv= e=20 them the freedom to chose that framework then. about fragmentation in the multimedia apps: It probably cannot get worse than what we have now with apps using=20 mplayer/xine/gstreamer/aRts. And it probably wouldn't if we choose one=20 backend since the will always be apps using something different than the KD= E=20 core. =2D-=20 C'ya Matthias ________________________________________________________ Matthias Kretz (Germany) <>< http://Vir.homeip.net/ MatthiasKretz@gmx.net, kretz@kde.org, Matthias.Kretz@urz.uni-heidelberg.de --nextPart1162205.mI65SVBIEn Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBBPBx+yg4WnCj6OIoRAgEeAJ9oDi2NDnKQJ2LS77mIaBySqJr1OACfTxDr yfsoi684ZD9J5DnuKI9nIdw= =8i+o -----END PGP SIGNATURE----- --nextPart1162205.mI65SVBIEn-- --===============0738437290== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ kde-multimedia mailing list kde-multimedia@kde.org https://mail.kde.org/mailman/listinfo/kde-multimedia --===============0738437290==--