Snappy GUI response
"GrayShade" <[email protected]> Sat, 1 Jul 2006 09:57:42 +0300
| Newsgroups | gmane.comp.xfree86.forum |
|---|---|
| Message-ID | <001501c69cdb$a670d0a0$5c167e56@mycomp> |
This is a multi-part message in MIME format. ------=_NextPart_000_0012_01C69CF4.CBA10AC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Maybe this comes a few years too late, but I didn't really see things = change in good.. In my opinion, the problem in not really in the X server, but in the way = the toolkits (GTK+, QT) handle the redraws. Someone proposed the suggestion of using a backing store to speen up the = application display. But this isn't a solution if the window content has = changed. A window resize or drawing a menu will still blow up things. But someone should try a simple benchmark: make a window with two or = three tabs, add some GUI elements in each tab (buttons, text, listviews) = and cycle through them a million times. Port it to Win32/GTK+, = Win32/MFC, Win32/API, .NET, QT, GTK+, whatsoever. Of course: Win32/* doesnt manage the layout like GTK does; but this = could still be a way to measure performance and look for things to = optimize. And.. the Windows programs could be run using Wine. Yes, it = will slow down things a bit, but it could be a way to measure the = influence of the X Server. ------=_NextPart_000_0012_01C69CF4.CBA10AC0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2900.2912" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>Maybe this comes a few years too late, = but I didn't=20 really see things change in good..</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>In my opinion, the problem in not = really in the X=20 server, but in the way the toolkits (GTK+, QT) handle the = redraws.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Someone proposed the suggestion of = using a backing=20 store to speen up the application display. But this isn't a solution if = the=20 window content has changed. A window resize or drawing a menu will still = blow up=20 things.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>But someone should try a simple = benchmark: make a=20 window with two or three tabs, add some GUI elements in each tab = (buttons, text,=20 listviews) and cycle through them a million times. Port it to = Win32/GTK+,=20 Win32/MFC, Win32/API, .NET, QT, GTK+, whatsoever.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Of course: Win32/* doesnt manage the = layout like=20 GTK does; but this could still be a way to measure performance and look = for=20 things to optimize. And.. the Windows programs could be run using Wine. = Yes, it=20 will slow down things a bit, but it could be a way to measure the = influence of=20 the X Server.</FONT></DIV></BODY></HTML> ------=_NextPart_000_0012_01C69CF4.CBA10AC0--