Qt 3.2 requirement

Chris Howells howells at kde.org
Thu Jul 24 23:16:34 BST 2003

Hash: SHA1


On Wednesday 23 July 2003 20:53, Ian Reinhart Geiser wrote:
> Well as it is we cannot build KDE libs without Qt 3.2 and every day someone
> contributes another UI file or tidbit of code that is only in 3.2.  I guess
> what im getting at is maby we need to be more clear that we are using Qt
> 3.1.x until further notice.

I would like to see a Qt 3.2 requirement as soon as possible.

* Testing with Qt 3.2 will hopefully reduce the number of bugs in it leading 
to a nice stable Qt 3.2 when KDE 3.2 is released (still a while off I know).

* Having most of the developers using Qt 3.2 and a few using 3.1 is a mess, 
with Qt 3.2 depending code creeps into CVS regularly. I don't think it's 
going to be possible to stop that from happening, leading to moaning from 
those still using 3.1

* I want to commit KSplashScreen, based on QSplashScreen but with the option 
to globally turn off all splash screens, and remove all custom splash screens 
and replace them with KSplashScreen if possible.

- -- 
Cheers, Chris Howells -- chris at chrishowells.co.uk, howells at kde.org
Web: http://chrishowells.co.uk, PGP ID: 33795A2C
KDE/Qt/C++/PHP Developer: http://www.kde.org
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)


More information about the kde-core-devel mailing list