NSTextField performance [was: Xcode + Leopard at WWDC this year]
NSTextField performance [was: Xcode + Leopard at WWDC this year]
- Subject: NSTextField performance [was: Xcode + Leopard at WWDC this year]
- From: Chris Espinosa <email@hidden>
- Date: Fri, 21 Jul 2006 07:56:04 -0700
On Jul 21, 2006, at 5:59 AM, Stefan Werner wrote:
I suspect the problem is that the underlying Cocoa / Unicode / Quartz text layer has some major inefficiencies, and that fixing that is not a priority for the team that look after it because Xcode users are not a big population.
It is indeed a Quartz problem, as any Shark trace will confirm. NSTextField is known to favor pretty over fast, and hence is spending a the majority of time in complex text rendering functions to get ligatures, kerning etc right. None of which matters for C++ source code. That's why Xcode should not be using it, and rather use a Carbon text control like BBEdit or a custom Cocoa text field like TextMate. NSTextField is a great help for formatted richt text. But until gcc accepts RTF as input files, it's wrong tool IMHO.
This subthread has now drifted well out of Xcode territory and into general Mac OS X architecture issues, and should be conducted elsewhere.
|
_______________________________________________
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