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+.
Thread beginning with comment 348998
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: QT does not get it right
by MacMan on Sat 14th Feb 2009 21:11 UTC in reply to "RE: QT does not get it right"
Member since:

I have tried it, and no it technically does not use Cocoa

It works like QT does on all other platforms, it essentially, just creates a single Cocoa window, then does all of its own drawing to this window. It essentially just draw to a single pixmap per window, then just uses Cocoa to draw the pixmap to the screen.

This is precisely why it looks so strange, because it has all of its own controls and widgets instead of using the native OS widgets. This may not be so bad on Unix, where QT can be considered the native widget set, as X11 really does not provide for widgets, just a port to draw stuff to.

Reply Parent Score: 2

adkilla Member since:

What do you mean it doesn't look native? Specific examples?

We have clients using our Qt apps for vision research on Macs. They couldn't tell any difference. One of them has OCD and any Mac app not behaving like one drives him nuts. In fact when coupled with the unified toolbar look they couldn't tell any difference whatsoever.

You ought to try out the examples that come with the RC release and post the discrepancies here. That would be a more useful comment.

By the way, I have often seen comments like yours even for wxWidget apps. wxWidgets uses native carbon widgets like SWT.

I guess you can't please the Cocoa nazis.


Reply Parent Score: 3

MacMan Member since:

What do you mean it doesn't look native? Specific examples?

I guess you can't please the Cocoa nazis.

Does not look native? well, text does not line up in edit boxes, none of the controls line up correctly, etc...

One of the biggest reasons I use a Mac is for Cocoa / Objective-C. On linux I use GNUStep, which is not bad, but still needs a bit of work.

One of the big reasons I still use Windows, is C# / DevStudio is such a nice development env, although WinForms with Mono is definitely coming along nicely.

So, I guess your right about not pleasing the Cocoa nazis if thats what you want to call me. So I suppose say you had a really nice car you really liked to drive, and someone came along and said we are going to take your nice car, and you have to drive a Yugo or a Pinto because they were the lowest common denominator, and you did not want to give up your nice car, then I suppose that they might call you a car nazi?

Edited 2009-02-15 19:45 UTC

Reply Parent Score: 1