Trolltech has released the first bugfix release for Qt 4, the major release on which KDE 4 development is based on. Among the over 450 bug fixes and optimizations are numerous improvements to raster engine, X11 engine and QPainterPath, significantly speeding a range of drawing processes and introduction of top-level window transparency on X11.
I'm waiting KDE 4 to start learning how to code for QT, I've tryied once but I was lacking the necessary skills (C++), even like this, I found that Qt3 was great. I belive Qt4, even more thanks to the Windows GPL version will rock more and more.
There is no need to wait for KDE4 for that.
Just go and start learning Qt4 right now :-)
When KDE4 comes out you already know Qt and can start coding for KDE4 right away. You can even help with KDE4 if you want.
I'd suggest to learn Qt before diving into KDE technologies anyway, so don't lose time! ;-)
I din't said I HAD to wait, but that I WILL wait, hehehe.
Once KDE4 is out binaries for Qt4 will be out for major Linux distros and it will be much easier to program using it.
But yes, there is no need for wait, you can compile Qt4 by hand or install the win32 version, it's just I'm too laizy for that ;)
I doubt a little bit that you will become a great developer, if the lazyness starts here already, but you could install SUSE Linux 10.0. Qt4 packages do exist there. Now you have no further excuses anymore ;)
Qt 4.0.0 packages also exist for 9.x SUSE versions (supplementary/KDE/update_for_9.3/development/)
Micha: "I doubt a little bit that you will become a great developer, if the lazyness starts here already"
At school they teach me that good programmers are lazy. ;) A good programmer is always looking for the most efficient way to accomplish something.
"At school they teach me that good programmers are lazy. ;) A good programmer is always looking for the most efficient way to accomplish something."
Well said ! :)
Undoubtedly he will be a great developer - as Larry Wall wisely commented, laziness is one of the three virtues of a programmer :-)
I like to lay back a bit and survey the field; this can appear to be laziness. Since he is busy with other, more important matters (like working to feed himself and passing his exams,) there is nothing wrong with waiting a bit to see how things develop. In the meantime he can start with reading QT 4 documentation.
I'm not sure I'd want to go to SuSE 10.0 just to get QT 4. SuSE Pro 9.3 is very stable. I downloaded QT 4 and built it on SuSE 9.3, but then encountered some incompatibility with KDE.
"I doubt a little bit that you will become a great developer, if the lazyness starts here already".
You know, it's not that I'm lazy at all, but I'm lazy at learning Qt4 because I have still to graduate on computer science, work to pay univercity, admin a cluster...
So, in the moments I have free, yes, I'm a hell of lazy ;)
And there are also qt4 packages available in Debian
one thing you shall learn early as a dev is, to install the packages you need yourself.
that is, go to trolltech.com, get your recent Qt4 (or just get qt-copy from KDE SVN), build it and use it.
The difference between Qt 3 and Qt 4 is limited to their API. And thats what API documentation is for, you can't expect yourself to memorize it.
So what I'm saying is, when it comes to learning Qt there isn't much reason to wait.
May I suggest you try Python and pyQT? I think you'll find both to be easy to learn, and highly rewarding.
I suggest to try ruby =)
Both python and Ruby are great.
However python forces you to get into good habits (whitespace matters!) that will make you a better programmer. Thus I consider it better for a first language.
If you already know how to program, you are doing yourself a disservice if you don't know both. (unless you know LISP)
Language wars are fun, but in the end they are all turning complete, and therefore what one can do the other can do. It is only a question of which makes the job easier.
ruby sucks, python4ever
well that was a constructive reply :)
As I commented earlier on OSNews.com:
> Somethings are praised best by a broad understatement
> that not all can understand. Ruby should be (and is)
> nutured by the ppl that know what it is capable of.
> Shouting around how good it is only messes up the
> userbase/community with n00bs.
When I stared _really_ using Ruby I was amazed, clean consistent and powerfull.
And the community around it is great!
To say that "ruby sucks" might be a good way to keep it hidden from the masses a bit longer.
QT can also be used from other languages, such as Python and Perl, so you don't need to use only C++!
Does somebody know where can I find the Debian packages (or if it exists)?
Qt 4.0.0 is already in SID so it's only a matter of days :-)
If you would like to use the new and fresh sources from Trolltech you could just build the sources yourself, it's really easy:
then when developing you use these env variables:
simple as that
Implemented support for window opacity.
Yes! Thank you Trolltech and (most likely) Zack!
This is what I was waiting for :)
"...This feature is only present on Mac OS X and Windows 2000 and up."
Is this all there is or did I miss something? Like "Linux" and "alpha channel" for instance?
Er, how about "introduction of top-level window transparency on X11"?
I think they haven't updated the documentation. If you look at the URL, it still says 4.0. I don't know if they change the documentation for minor point releases. Can't wait to try this out once I have a fast internet connection again.
Hmm? What has the kernel to do with transparency???
For some sad reason people think KDE/Qt/X11 is linux only...
I compiled it and ran qtconfig, but when I switch between the tabs
"Appearance", "Fonts" etc I can almost see the tab being painted (or filled with
the widgets (comboboxes etc)
So, visually, I don't notice the promised speedup.
Also at startup I can see how all is painted.
My box is an XP2200, with an nv card using theirs drivers on xorg6.8
Also, qtconfig takes almost a second to start, from cache! First cold startup
is 2-3 seconds...
/me disappointed :-(
I bet you linked the program with the _debug libs
Unfortunately not, and I built it with opengl support also.
What can the problem be?
[email protected]:/usr/local/Trolltech/Qt-4.0.1/bin$ ldd qtconfig
linux-gate.so.1 => (0xffffe000)
libQt3Support.so.4 => /usr/local/Trolltech/Qt-4.0.1/lib/libQt3Support.so.4 (0xb7c26000)
libQtGui.so.4 => /usr/local/Trolltech/Qt-4.0.1/lib/libQtGui.so.4 (0xb7753000)
libpng12.so.0 => /usr/lib/libpng12.so.0 (0x416bc000)
libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x419b5000)
libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x4199c000)
libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0xb7734000)
libXrender.so.1 => /usr/lib/libXrender.so.1 (0x4154e000)
libXrandr.so.2 => /usr/X11R6/lib/libXrandr.so.2 (0x41791000)
libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0x4177c000)
libXinerama.so.1 => /usr/X11R6/lib/libXinerama.so.1 (0xb7731000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x4192d000)
libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x4165c000)
libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x41881000)
libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x41558000)
libQtNetwork.so.4 => /usr/local/Trolltech/Qt-4.0.1/lib/libQtNetwork.so.4 (0xb76e8000)
libQtSql.so.4 => /usr/local/Trolltech/Qt-4.0.1/lib/libQtSql.so.4 (0xb76b3000)
libQtXml.so.4 => /usr/local/Trolltech/Qt-4.0.1/lib/libQtXml.so.4 (0xb766d000)
libQtCore.so.4 => /usr/local/Trolltech/Qt-4.0.1/lib/libQtCore.so.4 (0xb7536000)
libz.so.1 => /usr/lib/libz.so.1 (0x41625000)
libpthread.so.0 => /lib/tls/libpthread.so.0 (0xb7524000)
libdl.so.2 => /lib/tls/libdl.so.2 (0xb7520000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb743a000)
libm.so.6 => /lib/tls/libm.so.6 (0xb7414000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb7408000)
libc.so.6 => /lib/tls/libc.so.6 (0xb72d0000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0x416e3000)
Don't you have some issues with your fonts, because it loads at the same speed on my *so old* laptop.
try fc-cache as superuser to update your fonts.
Have a look there maybe:
I also thought it was slow.
I downloaded the open source edition for windows, and using Qt designer if you drag windows across the widget toolbox for example, it becomes sluggish and there is a white region where the window is redrawn (slowly).
Very dissappointed with the speed on windows. X11 speed seems ok (with Qt 3 - can't get that much slower though can it?).
And no there is nothing wrong with the machine. No font issues, no driver issues, and it is a fast machine (1.6 GHz/700MB RAM), so it is just Qt being slow.
Hope they improve it.