JUL
23
2003

Trolltech Releases Qt 3.2

The newest iteration of Qt has been released today. See the announcement on Trolltech's site. User desktop improvements include a "completely re-written, faster font rendering engine." Developer improvements include new QSplashScreen and QToolBox objects. Looks fun!

KDE developers will be pleased to hear that Qt 3.2 is available from the qt-copy CVS module. It is expected that Qt 3.2 will be

required
for KDE's main development branch (CVS HEAD) in the near future. It should be noted that 3.1.x versions of KDE experience some problems with Qt 3.2 and that for that reason this combination is not recommended.

Comments

I am experiencing some problems with my SuSE 8.2 freetype lib as it seems it is not possible to get antialiasing to work with truetype fonts (at least it works with type 1 fonts). Anybody here who has similar problems (and possibly a solution)?


By thomas at Wed, 2003/07/23 - 5:00am

Please post your support question to the: kde-linux list and we will try to help you.

--
JRT


By James Richard Tyrer at Thu, 2003/07/24 - 5:00am

So QT 3.2 will it make easiert to migrate old motif programs? Any experiences?


By Hein at Wed, 2003/07/23 - 5:00am

What is the nature of those problems? I thought Qt 3.x was supposed to be backwards compatible. Sounds like a serious bug.


By ac at Thu, 2003/07/24 - 5:00am

The important question is, does this fix the problems with font names?

--
JRT


By James Richard Tyrer at Thu, 2003/07/24 - 5:00am

Are developers interested in fixing KDE 3.1.x problems with QT 3.2, or are bug reports on this not welcome?


By cbcbcb at Thu, 2003/07/24 - 5:00am

they add a "Splashscreen" widget? wtf? so no KDE/QT applications have had splashscreens before this NEW feature? Sounds like bloat to me.


By autumn at Thu, 2003/07/24 - 5:00am

Well, it means that all apps don't need to roll their own splash implementation, thus reducing bloat.


By chakie at Thu, 2003/07/24 - 5:00am

The fact that KDE/Qt applications had to roll their own SplashScreen widgets is evidence that TT's customers wanted a SplashScreen widget in Qt..


By fault at Thu, 2003/07/24 - 5:00am

It's a trivial implementation. It doesn't cause any bloat. It is essentially a bare widget that displays a pixmap and starts a timer. At most it has 20 lines of real code.


By David Johnson at Thu, 2003/07/24 - 5:00am

It's better than a timed splash screen. This new splash widget displays automatically until the application is opened. Thus, no timer. It's automatic. Now, instead of a crappy timed splash screen in 20 lines, you can have a fully auto splash screen in 3 lines.


By zeroskill at Mon, 2003/07/28 - 5:00am

It's the opposite of bloat. Before applications that wanted a splash screen had to write one from scratch. Now applications can use QSplashScreen (or KDE developers the soon to be KSplashScreen) therefore reducing code duplication.


By Chris Howells at Fri, 2003/07/25 - 5:00am

How does this new font rendering engine fit in with freetype2, Xft, etc for X ?

Are these things complementary? mutually exclusive?

Can someone gimme a clue, please?


By and large at Thu, 2003/07/24 - 5:00am

I think it still uses freetype, Xft ... as usual... the only thing you could probably notice is that fonts are actually BIGGER while webbrowsing. Well, at least they are much bigger in the qt-copy verson I have right now.


By Unai at Thu, 2003/07/24 - 5:00am

Qt now recognises that fontconfig/Xft2 can artificially italicise fonts, so italics can now be selected for any font from font selection dialogues. :)

... At least I _think_ that's a new Qt feature. Not sure how long it's been there.


By Deciare at Fri, 2003/07/25 - 5:00am

Is KDE goign to lose pace with Qt, since 3.2 was released now and KDE still has at least 5 months until 3.2 will be released and by then there wil almost be a new version of Qt. IT would really suck if KDE couldn't keep pace with Qt like in teh past where the releases were almsot simultaneous.


By somebody at Sat, 2003/07/26 - 5:00am

Since when and why should there be a necessity to release KDE simultaneously to a new Qt version (which doesn't even fix known problems and thus forces KDE developers to work around them in KDE libs instead)?


By Datschge at Sat, 2003/07/26 - 5:00am