Re: KDE apps...

Post #120,712 by deSitter 10/10/03 1:13:26 AM Reply	Re: KDE apps... Yes, the default KDE themes are like Windows XP "Clown on Acid"(tm), but you can easily fix that, there are about a dozen widget sets to choose from in KDE 3 - my KDE widgets are basically CDE clones - simple Adode Sans MT font for menus and buttons etc. Very flat, minimal 3D, minimal shadowing. The antialiasing in Qt is so good that I can't live without it, and in fact I suppose my primary requirement from a machine of any type is the ability to make print-quality letters onscreen. I have one GTK2 app that has nice antialiased widgets and that looks OK as well. I think the color-explosion thing is a European taste - could be the drab weather and long winters - I seem to remember continental Europe as being generally garish. -drl
Post #120,717 by pwhysall 10/10/03 3:16:46 AM Reply	Antialiasing Not a function of QT. It's the Xft renderer. Any apps can use it, and do; The WindowMaker toolkit (WingS or something?) is now Xft enabled, for example. Peter [link\|http://www.debian.org\|Shill For Hire] [link\|http://www.kuro5hin.org\|There is no K5 Cabal] [link\|http://guildenstern.dyndns.org\|Blog]
Post #120,723 by deSitter 10/10/03 4:32:51 AM Reply	Not true The algorithm for painting characters derives from freetype, not Xft, which is X-server level font handling and makes no assumptions about the actual details of antialiasing of specific font types (in old X, fonts were displayed as on or off pixels, period - no shading possible). Qt interfaces directly to Xft, while GTK has a separate layer, Pango, for font handling. Because they both end up running through freetype via Xft, they both make nice looking fonts, but the use of it in Qt is thoroughgoing and properly low level, while typically GTK has a zillion complex interrelated APIs, like Windows, because it just seems to grow according to demand and not according to design, also like Windows. -drl

Welcome to IWETHEY!