From kde-core-devel Tue May 10 09:06:25 2011 From: "Aaron J. Seigo" Date: Tue, 10 May 2011 09:06:25 +0000 To: kde-core-devel Subject: Re: Qt5 -> KDE5? Message-Id: <3558470.jFf3Wh6UGO () freedom> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=130501844616229 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart2260379.vLWDXlkey8" --nextPart2260379.vLWDXlkey8 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="ISO-8859-1" On Tuesday, May 10, 2011 10:34:32 Thiago Macieira wrote: > KIO needs some love, but I don't think we should take the BC opportunity to > open the floodgates again. agreed, but i do think there is an opportunity here to try and separate the platform integration bits out of KIO. otherwise KIO almost becomes a non- starter for anything that isn't a desktop. we don't necessarily need to rework the API very much, just modularize the library so it is more reusable. my concern is that if we don't do this, we'll end up with a lot of applications marooned on the desktop or off the desktop due to have KIO (or not) or a lot of applications with multiple code paths for this functionality. (libplasma already has one such code path!) it might be tempting to say, "let's just find something else for non-desktop stuff" but we have so much code using KIO and it is a rather good API and library otherwise that it would be a damn shame to go that route. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks --nextPart2260379.vLWDXlkey8 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEABECAAYFAk3JABUACgkQ1rcusafx20N61gCeNi69m+gNbz28NUy07NnjXU9I SCIAnRpTsh6xCXui66VYgEJW4oMm84r9 =H9OW -----END PGP SIGNATURE----- --nextPart2260379.vLWDXlkey8--