From kde-core-devel  Sun Mar 12 17:12:44 2006
From: Thiago Macieira <thiago.macieira () trolltech ! com>
Date: Sun, 12 Mar 2006 17:12:44 +0000
To: kde-core-devel
Subject: Trolltech, Qt 4.2 and KDE 4.0
Message-Id: <200603121812.44586.thiago.macieira () trolltech ! com>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=114218369631259
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart1460375.TYhWplC9B4"

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

Hello everyone

Trolltech is aware that KDE 4.0 will require many features present in Qt=20
that are currently not there or not even scheduled for Qt 4.2. And we're=20
also aware of discussions going on about extending our classes to provide=20
that functionality and of patches being made against qt-copy in hope of=20
being rolled into Qt in the future.

While we have our own set of priorities and features for Qt 4.2, we are=20
committed to seeing KDE 4.0 happen and using an unpatched Qt 4.2, without=20
the need for crude hacks or unnecessary subclassing. Therefore, Trolltech=20
is placing one resource to interact with the KDE developer community and=20
finding out what such needs are.

This point of contact will be me: I want to hear from the developers what=20
changes to Qt as it currently stands is required in order to produce KDE=20
4.0. However, I won't be implementing those changes myself. I'll merely=20
relay the information to our developers and make sure it gets the=20
necessary and timely attention.

I'm already collecting such issues, like the QDate range extending or the=20
QAction necessary modifications. And apparently we have one more for=20
menus, being discussed right now on kde-devel.

I'd like to hear from the developer community what those features are,=20
what their use-cases are and how they affect Qt. I'd also like to know=20
what the solution would be if Trolltech were to not accept the feature:=20
how much impact would it have on KDE code.

What I don't want is bug reports on Qt. We have a team of support=20
engineers dedicated to assessing all bug reports sent to=20
qt-bugs@trolltech.com. All bug reports should go through the normal=20
channels. I'd like to be informed only of critical issues for *KDE*, for=20
which there is no simple workaround.

=2D-=20
Thiago Jos=E9 Macieira - thiago.macieira AT trolltech.com
Trolltech AS - Sandakerveien 116, NO-0402 Oslo, Norway

--nextPart1460375.TYhWplC9B4
Content-Type: application/pgp-signature

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

iD8DBQBEFFaMM/XwBW70U1gRAjCgAJ0f1IeoDhaGcrkRLdtLUZCorKfZlACeNorT
wa3i+pd6K+j2iIpa7u6JAnw=
=1AAJ
-----END PGP SIGNATURE-----

--nextPart1460375.TYhWplC9B4--