--nextPart1390211.KYJ81Wy0T7
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable

On November 2, 2010 19:05:09 Aaron J. Seigo wrote:
> On Monday, November 1, 2010, Diederik van der Boor wrote:
> > I can't stress enough it needs a good plan to limit impact on apps.
>=20
> this would be absolutely critical indeed.
>=20
> something that is completely opaque to me in this discussion so far is
> whether the idea is to:
>=20
> a) grind kdelibs into a fine dust of classes, rename some from KFoo to QF=
oo
> (and all the Qtification that implies) and reorganize the remainder (which
> should be a minimal set) into a new set of K* libs
>=20
> or
>=20
> b) define a new set of granularities for libraries in kdelibs (non-ui,
> desktop, framework, etc.) and split up our existing classes along those n=
ew
> lines, keeping names largely in place
>=20
> or
>=20
> c) do a bit of (a) and (b), and if so what the guidelines for deciding wh=
en
> to do (a) and when to do (b) are
>=20
> probably because it isn't a concrete plan yet, but rather a general
> proposal. these are the kinds of details that are needed before we can
> move on.

hmm, rereading=20
http://techbase.kde.org/index.php?title=3DProjects/KDELibsModifications
it seems to suggest splitting into only two modules.

it doesn't talk about spiltting down the non-platformy stuff further...=20
although it does mention tiers. Steveire, are the tiers meant to be actuall=
y=20
separate, or what?

=2D-=20
Chani
http://chani.ca

--nextPart1390211.KYJ81Wy0T7
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)

iEYEABECAAYFAkzQaMIACgkQeGbAwpIS3GzSlgCfS7+7lnJ3k/PexiBDvK15AjRL
kNoAniNZt7bmIneZGRW3NijOhMDRzEGz
=JAnm
-----END PGP SIGNATURE-----

--nextPart1390211.KYJ81Wy0T7--