Linked by lopisaur on Fri 25th Jun 2010 22:21 UTC
Thread beginning with comment 431683
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2006-06-12
Also, KDE/Qt apps can be used with the other Xorg server: XFBdev with little performances penality while Gnome/GTK app can't be used at all with resolution higher than 2x2. Qt is able to ask the framebuffer to update a bunch of pixel (at once) directly, while GTK redraw the whole screen pixel per pixel. So I can browser the web or watch a video on the framebuffer or scroll thumbnails in dolphin at more than 24fps while GTK can not even draw them in less than 2 second per frame.
It is when you really see how well Qt work and how well it is integrated in X.
You have no GPU but a lot of CPU? Fine, it will use the raster backend and draw the window as if it was a moving image (bitmap).
You have normal needs or networked ones? Fine, the X11 backend will use the protocol in a efficent way to draw the window (like in my xfbdev example)
Have a good GPU or want to save energy in a smartphone with efficient GPU and hungry CPU? The hardware accelerated OpenGL backend is there for you (but a little experimental).