Home > GTK+ > GTK+ 2.0.5 Released GTK+ 2.0.5 Released Eugenia Loli 2002-06-16 GTK+ 7 Comments One day after the release of GTK+ 2.0.4, the team releases GTK+ 2.0.5 which fixes a couple of important bugs. Read the announcement here, and also read the announcements for GLib & GTK+ 2.0.4 and Pango 1.0.2. About The Author Eugenia Loli Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker. Follow me on Twitter @EugeniaLoli 7 Comments 2002-06-16 8:00 pm Question, how widely used is the Win GTK port, & howdoes it compare with the native version? or stack up against other x platform libs? And since it is on their website, I hope one day the BeOS version can get restarted after R1 is out. I am assuming 2nd time around would be alot easier with R1 source in hand. Also note that D Reid the original BeGTK porter is doing great work on the OBOS networking team! See the OBOS kernal boot up screen shot on BeOSjournal.org. 2002-06-16 8:38 pm The Windows GTK+ port is bad. Very-very slow on redraw/blitting, plus it looks ugly and alien under Windows, because it does not use the native widgets… I would say that GTK+ really needs X11 as it is very tight to the X architecture, and if a port is done without the use of X (like in the case of Windows), the port won’t be as good as the original… 2002-06-17 8:26 am Porting GTK+ wouldn’t be a good idea, but creating a brand new implementation for Windows, BeOS and so on would be wiser. Besides, GTK+ isn’t that great a API, unless you want to write a C graphical app without making your own libraries. If you want cross platform anyway, choose QT. But then if you can’t stand not having a GPL version for each platform, why not use wxWindows? 2002-06-17 10:33 pm Off the top of my head, the only application I can think of that uses GTK for Windows is GIMP. And as Eugenia pointed out, the GTK toolkit in Windows is pretty ugly and slow. It’s also buggy. I’ve experienced such problems as pull down menus that fail to close until you tear the menu off and click the close button, dialog boxes where the buttons are non-functional until you move the window and have it redrawn, etc. If you are looking for decent cross platform toolkit, you might want to try FOX. It’s widgets look a lot like the Windows native widgets and it has been ported to several platforms. It also includes bindings for several languages including C++, Perl, Python, and Ruby. 2002-06-17 11:28 pm Thanks for the comments, I’m inclined to agree about Qt, I am shamed to say I only noticed the BeOS port of Qt 2.3.0 by Zenja a short time ago even though it was on BeBits a yr ago, but it needs Bone! Stupid question?, I know that all the insiders got Bone, is it possible to get this so I could play with this Qt port? Also even if it worked for regular non Bone, wouldn’t there still be license issue with TrollTech or is it way below radar? and did anybody ever try out this port? 2002-06-18 12:01 am The Qt port of BeOS does not only need BONE, but it also needs the ugly, slow and buggy implementation of X11 for BeOS. In other words: use and program for Qt under Unix/Linux/Windows and Mac but *not* under BeOS. 2002-06-18 9:23 am Is the GTK 2.x versions speedier than the GTK 1.x versions?