http://www.osnews.com/story/16062/GNOME_2_16_1_Released Exploring the Future of Computing en-us Copyright 2001-2013, David Adams adam+nospam@osnews.com Sun, 19 May 2013 12:42:19 GMT http://www.osnews.com/images/osnews.gif http://www.osnews.com http://www.osnews.com/thread?168392 http://www.osnews.com/thread?168392 Slightly offtopic here... But it's always bothered me that the win32 builds and such of GTK+ always lag behind. (Seems now its at 2.8.20, according to the GTK+ For Win32 page on gtk.org)

It would be nice if the cross-platform-ness of this cross-platform toolkit was a little more up to date. Wed, 04 Oct 2006 20:44:00 GMT donotreply@osnews.com (mrcool) Comments http://www.osnews.com/thread?168397 http://www.osnews.com/thread?168397 Well, judging by Sylpheed 2.3 beta2 which uses GTK+ 2.10.4, problems with screen garbage, slow redraw and not using native file dialog still remain :- Wed, 04 Oct 2006 20:52:00 GMT donotreply@osnews.com (Temcat) Comments http://www.osnews.com/thread?168434 http://www.osnews.com/thread?168434 It'd also be nice if GTK+ got out of 1998. Seriously, it makes my 1400x1050 resolution LCD look like 800x600 no matter what font or theme I use (I basically get variations between absurdly oversized and ridiculously large). It'd also be nice if it was fast, but I think that's asking too much of the GNOME folks (after all, it might confuse users). Wed, 04 Oct 2006 21:37:00 GMT donotreply@osnews.com (siride) Comments http://www.osnews.com/thread?168520 http://www.osnews.com/thread?168520 Tracker support in Nautilus, it's in Edgy and it's blazing fast. Nautilus search found over 6000 png images in about 10 seconds and finds stuff in under a second.

http://jamiemcc.livejournal.com/3782.html Thu, 05 Oct 2006 01:18:00 GMT donotreply@osnews.com (SlackerJack) Comments http://www.osnews.com/thread?168649 http://www.osnews.com/thread?168649 I never had any problem with Sylpheed ...
Anyway, what does Sylpheed use of GTK+ has to do with GTK+ efficiency ?!
Speaking of use of native dialog, I think you're talking about Windows version of GTK+, which explains why I don't see the same problems as yours.
Though I don't have any of these problems (redraw, garbage) with Wireshark nor Ethereal on Windows. Thu, 05 Oct 2006 11:30:00 GMT donotreply@osnews.com (Ookaze) Comments http://www.osnews.com/thread?168675 http://www.osnews.com/thread?168675 It'd also be nice if GTK+ got out of 1998. Seriously, it makes my 1400x1050 resolution LCD look like 800x600 no matter what font or theme I use (I basically get variations between absurdly oversized and ridiculously large)

I think you are still living in 1998, unless I didn't understand what you mean. The right behaviour is that the font or theme you choose should not change because you change display medium. Your fonts should be the same size on a 800x600 and on a 1400x1050. It should just be more readable on the 1400x1050 display.
I mean, your 12 pt font should be 12 pt everywhere (screen, paper, ...). So on my 1600x1200 display, Gnome looks big because I use 10 pt fonts, but 8 pt (or lesser) fonts are perfectly readable even with Gnome's antialiasing on at these sizes.

It'd also be nice if it was fast, but I think that's asking too much of the GNOME folks (after all, it might confuse users)

And I wonder what you mean there ... When I hear people like you, it sounds like you hit the cairo corner cases every single time you make a desktop action ! Thu, 05 Oct 2006 13:04:00 GMT donotreply@osnews.com (Ookaze) Comments http://www.osnews.com/thread?168701 http://www.osnews.com/thread?168701 Anyway, what does Sylpheed use of GTK+ has to do with GTK+ efficiency ?! Speaking of use of native dialog, I think you're talking about Windows version of GTK+, which explains why I don't see the same problems as yours.

You see, the thread is called "GTK+ & Win32". I don't see these problems in Linux version of Sylpheed, ergo GTK+ is the culprit here. BTW I incorrectly used the term "screen garbage"; what I actually meant was areas inside of the application windows that didn't redraw and various artifacts like stripes etc. You can observe them by for example resizing the right pane of Sylpheed window. Thu, 05 Oct 2006 14:30:00 GMT donotreply@osnews.com (Temcat) Comments http://www.osnews.com/thread?168708 http://www.osnews.com/thread?168708 You see, the thread is called "GTK+ & Win32"

That's why I talked about Ethereal and Wireshark.

I don't see these problems in Linux version of Sylpheed, ergo GTK+ is the culprit here

I wonder. I would say the Windows backend is the problem here (what is it called ? GDI ?), not GTK+ by itself.

BTW I incorrectly used the term "screen garbage"; what I actually meant was areas inside of the application windows that didn't redraw and various artifacts like stripes etc. You can observe them by for example resizing the right pane of Sylpheed window

It could be Sylpheed or Windows too, as I don't see that on Windows with the few GTK+ apps I use on it at work. And I can tell you wireshark (or ethereal) is loaded with frames (130k+ frames), and uses native Windows file dialog. Ethereal, an older build, uses GTK+ file dialog. I wonder if this is really a GTK+ Windows limitation, or just an application developer choice of API. Thu, 05 Oct 2006 14:51:00 GMT donotreply@osnews.com (Ookaze) Comments http://www.osnews.com/thread?168716 http://www.osnews.com/thread?168716 I wonder. I would say the Windows backend is the problem here (what is it called ? GDI ?), not GTK+ by itself.

I would say it is GTK's usage of GDI ;-) Because wxWidgets for example don't demonstrate this behavior. But I did observe something similar in at least one other GTK+ application, namely Gimp for Windows.

And I can tell you wireshark (or ethereal) is loaded with frames (130k+ frames)

Quite possible, if the frames contain just images, not GTK+ widgets.

and uses native Windows file dialog.

Interesting. Then I wonder whether it is an existing option in GTK's or just an ad hoc hack. If it is the former, then I'll file a bug against Sylpheed so it requests the native dialog in Windows.

I wonder if this is really a GTK+ Windows limitation, or just an application developer choice of API.

"Application developer choice of API" here is GTK+, isn't it? ;-) After all, the widgets are the same in Linux. Again, I would rather say that it's the way GTK uses GDI. Because it really shouldn't happen. Thu, 05 Oct 2006 15:17:00 GMT donotreply@osnews.com (Temcat) Comments