Linked by Thom Holwerda on Sat 14th Feb 2009 12:55 UTC
Google A major complaint about Google's Chrome web browser has been that so far, it is still not available on anything other than Windows. Google promised to deliver Chrome to Mac OS X and Linux as well, but as it turns out, this is a little harder than they anticipated, Ben Goodger, Google's Chrome interface lead, has explained in an email. It has also been revealed what toolkit the Linux version of Chrome will use: Gtk+.
Permalink for comment 348895
To read all comments associated with this story, please click here.
RE[2]: Why not QT?
by silix on Sat 14th Feb 2009 15:15 UTC in reply to "RE: Why not QT?"
silix
Member since:
2006-03-01

They didn't say that QT was bad... they said they wanted to use the native toolkit. So the question is: what is the native toolkit on Linux?
interestingly, the answer is none, since unix' (and then linux') gui system has been designed the way it is (i.e. as modular as it can be, with widget look and feel implemented at the toolkit level) just to avoid being tied to a single toolkit, thus to have no "native", privileged, toolkit

if there's a native toolkit on unix/linux, that may have been AWT, but nobody has used it for ages and it has afaik been deprecated in 7.x Xorg releases -
apart from that, the next layer in the stack, ie the X11 protocol binding (Xlib or XCB )used to be considered the native gui library
but at a time high level widget libraries are designed to be crossplatform, and are given non-X11 rendering backends even on linux, that doesnt hold true any longer

Edited 2009-02-14 15:22 UTC

Reply Parent Score: 3