• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Xcode & Visual C++
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode & Visual C++


  • Subject: Re: Xcode & Visual C++
  • From: Ladd Van Tol <email@hidden>
  • Date: Fri, 6 Jan 2006 14:51:05 -0500


On Jan 6, 2006, at 9:56 AM, Trenton Schulz wrote:

Not to nitpick here, but Qt 3.0 used to "emulate" the drawing of widgets. Qt 3.1 and on used AppearanceManager to render widgets and Qt 4.x uses HIThemes for this job. In the end, we have the same flaws in drawing that other Carbon controls do. I know, I've filed bugs against it [HITheme].

Qt 4 is actually built using HIView and lots of the other goodness that comes from the HIToolBox. As we tighten up our architecture, it should really start to fly.

We (Trolltech) have seen this "Qt emulates drawing on the Mac" so many times and it hasn't been true for years. Sometimes you just have to set the record straight. Of course, there's room for improvement, but that's true of all software :)

It seems to me that the default button behavior was non-standard still on Qt 3.3.3. When I tried it, the button was the wrong shade of blue, and pulsed at the wrong rate. Additionally, there were a lot of weaknesses in the Mac implementation of the framework, like not being able to dynamically add items to a menu. While Qt is a workable solution on Linux, I have yet to see a Mac application done in Qt that looked even remotely close to Aqua-compliant. I have yet to use Qt 4.0 -- hopefully things have improved as Trenton describes.


Qt's GUI builder is also rather opaque, and does not play well with external editors when run on the Mac -- it seems to assume that it will be the only tool used to edit C++ source. This causes a lot of edit clobbering issues that would be hilarious if they didn't wipe out hours of work. Basically, I would trust Qt on the Mac a lot more if the Qt tools actually looked and worked like good Mac applications. As of 3.3, they did not.

Because of these, and other problems, it is far faster and easier for me to write a separate Cocoa UI for the Mac version of a product that to try to make the GUI cross-platform. Additionally, the Cocoa UI will look better and perform better than the Qt equivalent.

- Ladd

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Xcode & Visual C++
      • From: David Young <email@hidden>
References: 
 >Re: Xcode & Visual C++ (From: David Michael Bryson <email@hidden>)
 >Re: Xcode & Visual C++ (From: Trenton Schulz <email@hidden>)

  • Prev by Date: Avoiding destructors while still calling atexit handlers
  • Next by Date: Re: Qt on OS X (was Xcode & Visual C++)
  • Previous by thread: Re: Xcode & Visual C++
  • Next by thread: Re: Xcode & Visual C++
  • Index(es):
    • Date
    • Thread