The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
|
Over 40 comments listed.
Printing out index only. |
KDE leads the future in Desktop Environments
by A. A. on Thursday 09/Jun/2005, @03:57
|
I am compiling KDE svn trunk on a nightly basis with my own scripts and it really rocks. I am here to thank everyone from the KDE team (and the cool people from #kde-devel) for their carefully work on keeping svn trunk always in shape. There are rarely any issues with svn trunk and it usually compiles over night without any issues. Rarely you need to do some manual work to have it finish the compile and the committs to svn trunk are usually tested and work. Thanks to the people for having created a nice, round and feature complete Desktop Environment for the Open Source world to get serious business, science and normal work done. Stuff that feel mature, complete, consistent and truly integrated.
|
[
Reply To This | View ]
|
|
|
decoration and theme
by naomen on Thursday 09/Jun/2005, @04:16
|
It is nice of the person for doing screenshots,
but me thinks that it is better for doing them
in the default window decoration, theme and
iconset.
|
[
Reply To This | View ]
|
|
|
Looks good!
by Jim on Thursday 09/Jun/2005, @04:23
|
I cannot stress enough how important ad-blocking is. I'd never consider using any browser that didn't have something similar to Firefox's AdBlock.
I think Konqueror would also gain a lot more users if it was easier to extend. The extensions I have installed are the main thing keeping me on Firefox.
With Firefox, you can just write a bit of Javascript and XML. With both Firefox and Opera, you can add features by writing a few lines of Javascript with Greasemonkey/user Javascript.
How much quicker would this Konqueror ad-blocking have come about if Konqueror was as easy as Firefox to extend?
Does anybody know if there is ongoing development of KaXUL? Or has it been abandoned?
|
[
Reply To This | View ]
|
|
|
KDE Start MENU
by fast_rizwaan on Thursday 09/Jun/2005, @05:17
|
So, at last after many years, KDE Developers got the courage to have Icon+Text! Congrats, but make it beautiful, attractive, customizable, animated. Support MNG and GIF for K button. Allow 4 state png/mng for k buttons! unfocused, focused(hover), pressed (focused), pressed (not hover).
Congrats on becoming bold!
|
[
Reply To This | View ]
|
|
|
feel?
by ch on Thursday 09/Jun/2005, @06:36
|
how does the new kde *feel* ?
|
[
Reply To This | View ]
|
|
|
Yuck
by mikeyd on Thursday 09/Jun/2005, @07:27
|
I was trying to enjoy the new Qt but all I could think was "Arrgh, motif's coming back!" Seriously, that theme is _horrible_.
|
[
Reply To This | View ]
|
|
|
Vertical text Sucks...
by Tim on Thursday 09/Jun/2005, @08:07
|
>>(KMix has a separate tab for device switches.)
Just like GNOME too.
And why dont get rid of th annoying Vertical Text?
|
[
Reply To This | View ]
|
|
|
may I ask, what distro?
by Timmeh on Thursday 09/Jun/2005, @10:16
|
nice preview. I really like how things are coming along. The vector demo looks really nice. there is also some qt4 preview stuff at the digitalfanatics qt4 website, but it's geared more towards programmers.
kinda off topic, but I'm just curious, what distro are you using?
|
[
Reply To This | View ]
|
|
|
Qt4 SUCKS!!! Please go back to Qt3!
by Daelin the Cruel on Thursday 16/Aug/2007, @09:38
|
While attempting to port a medium-sized program to Qt4, I noticed a SEVERE drop in performance. To diagnose this droppage, I wrote a very small, simple program that depicts two rectangles bouncing around on the screen, and reports the framerate (which is calculated as an average over 5 seconds).
Under both versions of Qt, the program used a QTimer widget to control the movement of the rectangles. The Qt3 version can simply draw the rectangles directly from the QTimer handler, while the Qt4 version must generate a paintEvent, which I tried both with the "update()" method (which supposedly waits until Qt's main loop to call paintEvent normally), and with the "repaint()" method (which supposedly calls paintEvent immediately, which is supposed to be faster but more likely to flicker).
On my machine (A 1-GHz Celeron with a low-end Radeon, resolution 1400x1050, 16bpp), both versions run fast when the window is at its default size (49 FPS-- the target framerate).
When the window is maximized, however, Qt4 takes a 39% performance hit (19 FPS), while Qt3 takes no hit at all!
In larger programs with lots of widgets (such as the program I was porting when I first noticed the problem), I notice that any use of a timer-updated widget drags the program to a near halt.
I have attached the program, so you can see for yourself that Qt4 really is inferior. It must be built with the $QTDIR environment variable set appropriately. Two Makefiles are required because MOC doesn't pay attention to #ifdef directives. You must run 'make clean' between building the demo with Qt4 and Qt3.
qtprog.tar.bz2
1KB (1875 bytes)
|
[
Reply To This | View ]
|
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
Posted by Matt Proud on Thursday 09/Jun/2005, @03:21