From kde-core-devel  Fri May 27 21:04:19 2005
From: Thiago Macieira <thiago () kde ! org>
Date: Fri, 27 May 2005 21:04:19 +0000
To: kde-core-devel
Subject: Re: Qt4addons module?
Message-Id: <200505271804.28761.thiago () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=111722789707294
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart2994502.iWkihNqCiN"

--nextPart2994502.iWkihNqCiN
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Alexander Neundorf wrote:
>Another point is that if you change from a Qt to a KDE application, you
> get everything: the KDE config system, the various daemons start,
> KCmdLineArgs, etc.
>We have a lot of classes which are just enhanced Qt classes with no
> direct relation to the KDE framework which could very well be used by
> Qt-only apps.

If people want to copy those classes into their programs and use them,=20
they are free to do so. The license is LGPL (or less) for a reason.

If we mount a library of "Qt-only useful classes", I think we'll end up=20
with libkdecore, just like David said. I didn't count, but I would bet=20
that the number of classes that don't compile/link/work on Windows is a=20
small minority when compared to the whole.

On my side, I know that the socket classes don't work on Windows (and,=20
what's even more problematic, there are no Unix sockets on Windows). The=20
reason for that is that I don't know the winsock API and have no=20
intention of learning.

=2D-=20
  Thiago Macieira  -  thiago (AT) macieira (DOT) info
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

2. T=F3 cennan his weorc gearu, ymbe se circolwyrde, wear=F0 se c=E6gbord a=
nd se=20
leohtspeccabord, and =FEa m=FDs c=F3mon lator. On =FEone d=E6g, he hine res=
te.

--nextPart2994502.iWkihNqCiN
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQBCl4tcM/XwBW70U1gRAlVbAJ9IU0zlnfLEOerCAwFzFc8hegbopgCeOw5O
SVwghByZ+34qQU4ZpcvPSW4=
=ZkSF
-----END PGP SIGNATURE-----

--nextPart2994502.iWkihNqCiN--